CVE-2004-2238 Other in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2004-2238 and fix it if it is affected.
What it is: CVE-2004-2238 is a medium-severity vulnerability in n/a, published on 17 Jul 2005.
Exploitation: There is no known exploitation of CVE-2004-2238 in the wild and no public exploit code.
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-2004-2238/ (Markdown: https://insights.sbomify.com/CVE-2004-2238/index.md)
A reported format string vulnerability in vpopmail was determined to be a false positive because the format strings were static constants.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2004-2238?
CVE-2004-2238 is a medium-severity vulnerability in n/a, published on 17 Jul 2005.
Official description
Format string vulnerability in vsybase.c in vpopmail 5.4.2 and earlier has unknown impact and attack vectors. NOTE: in a followup post, it was observed that the source code used constants that, when compiled, became static format strings. Thus this is not a vulnerability
Which versions are affected by CVE-2004-2238?
How do I fix CVE-2004-2238?
No fix has been published for CVE-2004-2238 yet. Limit exposure of the affected software until one is available.
Is CVE-2004-2238 being exploited?
There is no known exploitation of CVE-2004-2238 in the wild and no public exploit code.
Sources
Also known as GHSA-vgx4-x9cv-rgq3.