CVE-2004-2268 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2004-2268 and fix it if it is affected.
What it is: CVE-2004-2268 is a medium-severity vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2268 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-2268/ (Markdown: https://insights.sbomify.com/CVE-2004-2268/index.md)
Remote attackers can obtain the database password via debug information in rowLatex.inc.php, exposing sensitive credentials.
- 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-2004-2268?
CVE-2004-2268 is a medium-severity vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
PimenGest2 before 1.1.1 allows remote attackers to obtain the database password via debug information in rowLatex.inc.php.
Which versions are affected by CVE-2004-2268?
It affects 1 product.
Products include Pimentech Pimengest2.
How do I fix CVE-2004-2268?
No fix has been published for CVE-2004-2268 yet. Limit exposure of the affected software until one is available.
Is CVE-2004-2268 being exploited?
There is no known exploitation of CVE-2004-2268 in the wild and no public exploit code.
Sources
Also known as GHSA-3vxh-qpg8-h9j2.