CVE-2024-38453 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2024-38453 and fix it if it is affected.
What it is: CVE-2024-38453 is a high-severity vulnerability in n/a, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38453 exists.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2024-38453/ (Markdown: https://insights.sbomify.com/CVE-2024-38453/index.md)
Attackers can read an exposed API key in the Avalara for Salesforce CPQ app, potentially compromising integration security.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-38453?
CVE-2024-38453 is a high-severity vulnerability in n/a, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Avalara for Salesforce CPQ app before 7.0 for Salesforce allows attackers to read an API key. NOTE: the current version is 11 as of mid-2024.
Which versions are affected by CVE-2024-38453?
How do I fix CVE-2024-38453?
No fix has been published for CVE-2024-38453 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-38453 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38453 exists.
Sources
Also known as GHSA-6w4j-5cmh-9j58.