CVE-2013-0485 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2013-0485 and fix it if it is affected.
What it is: CVE-2013-0485 is a critical vulnerability in n/a, published on 21 Jan 2014.
Exploitation: There is no known exploitation of CVE-2013-0485 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-2013-0485/ (Markdown: https://insights.sbomify.com/CVE-2013-0485/index.md)
Unspecified vulnerability in IBM Java SDK class libraries with unknown impact and attack vectors.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2013-0485?
CVE-2013-0485 is a critical vulnerability in n/a, published on 21 Jan 2014.
Official description
Unspecified vulnerability in IBM Java SDK 7 before SR4-FP1, 6 before SR13-FP1, 5.0 before SR16-FP1, and 1.4.2 before SR13-FP16 has unknown impact and attack vectors related to Class Libraries.
Which versions are affected by CVE-2013-0485?
It affects 1 product.
Products include Ibm Java.
How do I fix CVE-2013-0485?
No fix has been published for CVE-2013-0485 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-0485 being exploited?
There is no known exploitation of CVE-2013-0485 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-9mgm-2qr8-pxgg.