Quick answers
- Is CVE-2024-47171 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-47171 being exploited in the wild.
- How severe is CVE-2024-47171?
- Low severity, with a CVSS score of 3.1, published 26 September 2024.
- Which products and versions are affected?
- agnai (npm) SEMVER:introduced=0,fixed=1.0.330.
- Is there a fix for CVE-2024-47171?
- Yes. agnai (npm): upgrade to 1.0.330 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-47171 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-47171?
- Check whether you run agnai (npm) 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
- agnai (npm): upgrade to 1.0.330 or later
npm install agnai@1.0.330
Technical details
This is a path traversal vulnerability (CWE-35, CWE-22) in the image upload handler. An attacker can inject path traversal sequences (e.g., encoded `../` segments) into the character ID parameter of a POST request to `/api/character`, which is then unsanitized and interpolated into the filename used by the `entityUpload()` function. The vulnerable code concatenates the attacker-controlled ID directly into the filename without path normalization, allowing traversal outside the intended upload directory. Exploitation requires authentication (low privilege) and network access to a public-facing Agnai instance; S3-backed deployments are unaffected. The vulnerability was fixed in version 1.0.330.
Affected products
- Agnai Agnai < 1.0.330
Identifiers
- CVE-2024-47171
- GHSA-g54f-66mw-hv66
Timeline
- 2024-09-26: disclosed
- 2024-09-26: patched: Fixed in version 1.0.330