CVE-2005-0521 Information disclosure in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2005-0521 and fix it if it is affected.
What it is: CVE-2005-0521 is a low-severity vulnerability in n/a, published on 23 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0521 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-2005-0521/ (Markdown: https://insights.sbomify.com/CVE-2005-0521/index.md)
Local attackers can read plaintext passwords from the data.eat file to gain elevated privileges in SendLink.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2005-0521?
CVE-2005-0521 is a low-severity vulnerability in n/a, published on 23 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
SendLink 1.5 stores sensitive information, possibly including passwords, in plaintext in the data.eat file, which allows local users to gain privileges.
Which versions are affected by CVE-2005-0521?
How do I fix CVE-2005-0521?
No fix has been published for CVE-2005-0521 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-0521 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0521 exists.
Public exploit code: 1 Exploit-DB entry.
Sources
Also known as GHSA-4g8g-4wc2-c33j.