CVE-2005-4524 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-4524 and fix it if it is affected.
What it is: CVE-2005-4524 is a medium-severity vulnerability in n/a, published on 28 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4524 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-4524/ (Markdown: https://insights.sbomify.com/CVE-2005-4524/index.md)
An attacker with low privileges can view private bug notes during resolution, leading to information disclosure in Mantis.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2005-4524?
CVE-2005-4524 is a medium-severity vulnerability in n/a, published on 28 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Mantis 1.0.0rc3 does not properly handle "Make note private" when a bug is being resolved, which has unknown impact and attack vectors, probably related to an information leak.
Which versions are affected by CVE-2005-4524?
How do I fix CVE-2005-4524?
Upgrade to a fixed version.
Is CVE-2005-4524 being exploited?
There is no known exploitation of CVE-2005-4524 in the wild and no public exploit code.
Sources
Also known as GHSA-v45h-m83x-7564.