CVE-2005-0508 Security feature bypass in n/a
Medium 4.6
Published
Updated
Check this codebase for CVE-2005-0508 and fix it if it is affected.
What it is: CVE-2005-0508 is a medium-severity vulnerability in n/a, published on 22 Feb 2005.
Exploitation: There is no known exploitation of CVE-2005-0508 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-0508/ (Markdown: https://insights.sbomify.com/CVE-2005-0508/index.md)
Attackers can bypass access controls in the Squiggle viewer for Batik by exploiting Rhino scripting engine security flaws.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is CVE-2005-0508?
CVE-2005-0508 is a medium-severity vulnerability in n/a, published on 22 Feb 2005.
Official description
Unknown vulnerability in Squiggle for Batik before 1.5.1 allows attackers to bypass certain access controls via certain features of the Rhino scripting engine due to a "script security issue."
Which versions are affected by CVE-2005-0508?
How do I fix CVE-2005-0508?
Upgrade to a fixed version.
Is CVE-2005-0508 being exploited?
There is no known exploitation of CVE-2005-0508 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2005-0508, GHSA-3c37-jjmv-92cc.