CVE-2025-62492

CVSS 6.5 Medium
  • CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Published: 2025-10-16T16:15:39.620

A vulnerability stemming from floating-point arithmetic precision errors exists in the QuickJS engine’s implementation of TypedArray.prototype.indexOf() when a negative fromIndex argument is supplied.

* The fromIndex argument (read as a double variable, $d$) is used to calculate the starting position for the search.

* If d is negative, the index is calculated relative to the end of the array by adding the array’s length (len) to d:

$$d_{new} = d + text{len}$$

* Due to the inherent limitations of floating-point arithmetic, if the negative value $d$ is extremely small (e.g., $-1 times 10^{-20}$), the addition $d + text{len}$ can result in a loss of precision, yielding an outcome that is exactly equal to $text{len}$.

* The result is then converted to an integer index $k$: $k = text{len}$.

* The search function proceeds to read array elements starting from index $k$. Since valid indices are $0$ to $text{len}-1$, starting the read at index $text{len}$ is one element past the end of the array.

This allows an attacker to cause an Out-of-Bounds Read of one element immediately following the buffer. While the scope of this read is small (one element), it can potentially lead to Information Disclosure of adjacent memory contents, depending on the execution environment.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2025-62492

CVE-2025-62492 is a medium severity vulnerability affecting the affected product.

Description: A vulnerability stemming from floating-point arithmetic precision errors exists in the QuickJS engine’s implementation of TypedArray.prototype.indexOf() when a negative fromIndex argument is supplied. * The fromIndex argument (read as a double variable, $d$) is used to calculate the starting position for the search. * If d is negative, the index is calculated relative to the […]

Exploit Difficulty: EASY
⏱️ Time to exploit: < 1 hour
🛠️ Required skills: Basic web security knowledge
💰 Public exploits: Likely available

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

EASY
⏱️ Time to Exploit: < 1 hour
🛠️ Skills Required: Basic web security knowledge
💰 Public Exploits: Likely available

Vulnerability Timeline

Oct 16, 2025
Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.