CVE-1999-0458 Information disclosure in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-1999-0458 and fix it if it is affected.
What it is: CVE-1999-0458 is a low-severity vulnerability in n/a, published on 29 Sep 1999. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0458 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-1999-0458/ (Markdown: https://insights.sbomify.com/CVE-1999-0458/index.md)
An attacker with local access can read password information from temporary files created by L0phtcrack in the system TEMP directory.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-1999-0458?
CVE-1999-0458 is a low-severity vulnerability in n/a, published on 29 Sep 1999. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
L0phtcrack 2.5 used temporary files in the system TEMP directory which could contain password information.
Which versions are affected by CVE-1999-0458?
It affects 1 product.
Products include L0pht L0phtcrack.
How do I fix CVE-1999-0458?
No fix has been published for CVE-1999-0458 yet. Limit exposure of the affected software until one is available.
Is CVE-1999-0458 being exploited?
There is no known exploitation of CVE-1999-0458 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-hm24-jp4w-ghvm.