CVE-2005-3112 Information disclosure in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2005-3112 and fix it if it is affected.
What it is: CVE-2005-3112 is a low-severity vulnerability in n/a, published on 30 Sep 2005.
Exploitation: There is no known exploitation of CVE-2005-3112 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-2005-3112/ (Markdown: https://insights.sbomify.com/CVE-2005-3112/index.md)
Attackers with database access can obtain plaintext passwords due to insecure storage in the reset password feature.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2005-3112?
CVE-2005-3112 is a low-severity vulnerability in n/a, published on 30 Sep 2005.
Official description
The "reset password" feature in Macromedia Breeze 5.0 stores passwords in plaintext in the database instead of the hash, which allows attackers with access to the database to obtain the passwords.
Which versions are affected by CVE-2005-3112?
It affects 1 product.
Products include Macromedia Breeze.
How do I fix CVE-2005-3112?
No fix has been published for CVE-2005-3112 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-3112 being exploited?
There is no known exploitation of CVE-2005-3112 in the wild and no public exploit code.
Sources
Also known as GHSA-g5f6-mfmg-v8r6.