Summary
Cache Poisoning Vulnerability
An attacker controlling the second variable of the translate function is able to perform a cache poisoning attack. They can change the outcome of translation requests made by subsequent users.
Details
The opt.id parameter allows the overwriting of the cache key. If an attacker sets the id variable to the cache key that would be generated by another user, they can choose the response that user gets served.
PoC
Take the following simple server allowing users to supply text and the language to translate to.
import translate from "translate";
import express from 'express';
const app = express();
app.use(express.json());
app.post('/translate', async (req, res) => {
const { text, language } = req.body;
const result = await translate(text, language);
return res.json(result);
});
const port = 3000;
app.listen(port, () => {
console.log(`Server is running on port ${port}`);
});
We can send the following request to poison the cache:
{"text":"I hate you", "language":{"to":"nl","id":"undefined:en:nl:google:I love you"}}
Now, any user that attempts to translate "I love you" to Dutch, will get "I hate you" in Dutch as the response.
Impact
An attacker can control the results other users may get
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2024-29042 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-29042? CVE-2024-29042 is a medium-severity improper input validation vulnerability in translate (npm), affecting versions < 3.0.0. It is fixed in 3.0.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- How severe is CVE-2024-29042? CVE-2024-29042 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of translate are affected by CVE-2024-29042? translate (npm) versions < 3.0.0 is affected.
- Is there a fix for CVE-2024-29042? Yes. CVE-2024-29042 is fixed in 3.0.0. Upgrade to this version or later.
- Is CVE-2024-29042 exploitable, and should I be worried? Whether CVE-2024-29042 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-29042 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-29042? Upgrade
translateto 3.0.0 or later.