CVE-1999-0539 Auth bypass in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-1999-0539 and fix it if it is affected.
What it is: CVE-1999-0539 is a critical authentication bypass vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0539 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-0539/ (Markdown: https://insights.sbomify.com/CVE-1999-0539/index.md)
Attackers can bypass authentication and access data on Unix hosts due to insecure trust relationships between systems.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-1999-0539?
CVE-1999-0539 is a critical authentication bypass vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A trust relationship exists between two Unix hosts.
Which versions are affected by CVE-1999-0539?
How do I fix CVE-1999-0539?
No fix has been published for CVE-1999-0539 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-1999-0539 being exploited?
There is no known exploitation of CVE-1999-0539 in the wild and no public exploit code.
Sources
Also known as GHSA-7v5h-pgc3-6pcp.