Quick answers
- Is CVE-2024-52809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-52809 being exploited in the wild.
- How severe is CVE-2024-52809?
- Medium severity, with a CVSS score of 4, published 2 December 2024.
- Which products and versions are affected?
- @intlify/core (npm) SEMVER:introduced=9.3.0,fixed=9.14.2; @intlify/core-base (npm) SEMVER:introduced=9.3.0,fixed=9.14.2; @intlify/vue-i18n-core (npm) SEMVER:introduced=9.3.0,fixed=9.14.2; petite-vue-i18n (npm) SEMVER:introduced=10.0.0,fixed=10.0.5; and 1 more.
- Is there a fix for CVE-2024-52809?
- Yes. @intlify/core (npm): upgrade to 9.14.2 or later; @intlify/core-base (npm): upgrade to 9.14.2 or later; @intlify/vue-i18n-core (npm): upgrade to 9.14.2 or later; petite-vue-i18n (npm): upgrade to 10.0.5 or later; vue-i18n (npm): upgrade to 9.14.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-52809 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-52809?
- Check whether you run @intlify/core (npm), @intlify/core-base (npm), @intlify/vue-i18n-core (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @intlify/core (npm): upgrade to 9.14.2 or later
npm install @intlify/core@9.14.2 - @intlify/core-base (npm): upgrade to 9.14.2 or later
npm install @intlify/core-base@9.14.2 - @intlify/vue-i18n-core (npm): upgrade to 9.14.2 or later
npm install @intlify/vue-i18n-core@9.14.2 - petite-vue-i18n (npm): upgrade to 10.0.5 or later
npm install petite-vue-i18n@10.0.5 - vue-i18n (npm): upgrade to 9.14.2 or later
npm install vue-i18n@9.14.2
Technical details
The vulnerability is a cross-site scripting (XSS) flaw combined with prototype pollution that affects vue-i18n's message compilation and rendering pipeline. When the library processes Abstract Syntax Tree (AST) objects generated by the message compiler, it does not properly validate prototype properties. An attacker can pollute Object.prototype with malicious properties that are then accessed during AST traversal and translation rendering, leading to arbitrary code execution. The attack requires either development mode usage or direct AST injection from an untrusted source; production builds using @intlify/unplugin-vue-i18n are typically protected by the build-time compilation process. User interaction is required (visiting a compromised page). Patches are available in versions 9.14.2, 10.0.5, and later for all affected packages.
Affected products
- Intlify vue-i18n 9.3.0 to 10.0.4
- Intlify @intlify/core 9.3.0 to 10.0.4
- Intlify @intlify/core-base 9.3.0 to 10.0.4
- Intlify @intlify/vue-i18n-core 9.3.0 to 10.0.4
- Intlify petite-vue-i18n 10.0.0 to 10.0.4
Identifiers
- CVE-2024-52809
- GHSA-9r9m-ffp6-9x4v
Timeline
- 2024-11-28: disclosed
- 2024-12-02: patched: Patches released: vue-i18n 9.14.2 and 10.0.5; @intlify/core 9.14.2 and 10.0.5; @intlify/core-base 9.14.2 and 10.0.5; @intlify/vue-i18n-core 9.14.2 and 10.0.5; petite-vue-i18n 10.0.5