CVE-2001-0608 Privilege escalation in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2001-0608 and fix it if it is affected.
What it is: CVE-2001-0608 is a high-severity vulnerability in n/a, published on 27 Jul 2001.
Exploitation: There is no known exploitation of CVE-2001-0608 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-2001-0608/ (Markdown: https://insights.sbomify.com/CVE-2001-0608/index.md)
An attacker with low privileges can exploit the AIFCHANGELOGON program in MPE/iX to gain additional privileges and access databases.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2001-0608?
CVE-2001-0608 is a high-severity vulnerability in n/a, published on 27 Jul 2001.
Official description
HP architected interface facility (AIF) as includes with MPE/iX 5.5 through 6.5 running on a HP3000 allows an attacker to gain additional privileges and gain access to databases via the AIF - AIFCHANGELOGON program.
Which versions are affected by CVE-2001-0608?
It affects 1 product.
Products include Hp Mpe.
How do I fix CVE-2001-0608?
No fix has been published for CVE-2001-0608 yet. Limit exposure of the affected software until one is available.
Is CVE-2001-0608 being exploited?
There is no known exploitation of CVE-2001-0608 in the wild and no public exploit code.
Sources
Also known as GHSA-vc9x-422x-j6wh.