Skip to content
Fencer Intel
medium 6.9

CVE-2024-52810 json

Prototype Pollution in @intlify/shared >=9.7.0 <= 10.0.4

published last yr. modified 4mo ago also EUVD-2024-3480 , GHSA-hjwq-mjwj-4x6c

cvss
6.9
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

@intlify/shared is a shared library for the intlify project. The latest version of @intlify/shared (10.0.4) is vulnerable to Prototype Pollution through the entry function(s) lib.deepCopy. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) as the minimum consequence. Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context. This issue has been addressed in versions 9.14.2, and 10.0.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Patch / fix

  • npm @intlify/shared 9.14.2, 10.0.5
  • npm @intlify/vue-i18n-core 9.14.2, 10.0.5
  • npm vue-i18n 9.14.2, 10.0.5
  • npm petite-vue-i18n 10.0.5
  • intlify vue-i18n 9.14.2, 10.0.5

Is CVE-2024-52810 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm @intlify/shared
>=9.7.0, <9.14.2
>=10.0.0, <10.0.5
9.14.2
10.0.5
npm @intlify/vue-i18n-core
>=9.7.0, <9.14.2
>=10.0.0, <10.0.5
9.14.2
10.0.5
npm vue-i18n
>=9.7.0, <9.14.2
>=10.0.0, <10.0.5
9.14.2
10.0.5
npm petite-vue-i18n
>=10.0.0, <10.0.5
10.0.5

Affected products

  • intlify vue-i18n

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of intlify/vue-i18n published their own advisory on GitHub. Reviewed sources take precedence over it.