# CVE-2007-0980: Auth bypass in n/a

> Remote attackers can obtain unauthorized access to HP Serviceguard for Linux, potentially leading to privilege escalation or data exposure.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-24qh-qr2h-95xw

## What is CVE-2007-0980?

CVE-2007-0980 is a critical authentication bypass vulnerability in n/a, published on 16 Feb 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Serviceguard for Linux; packaged for SuSE SLES8 and United Linux 1.0 before SG A.11.15.07, SuSE SLES9 and SLES10 before SG A.11.16.10, and Red Hat Enterprise Linux (RHEL) before SG A.11.16.10; allows remote attackers to obtain unauthorized access via unspecified vectors.

## Which versions are affected by CVE-2007-0980?

It affects 1 product.


Products: Hp Serviceguard for Linux.

## How do I fix CVE-2007-0980?

No fix has been published for CVE-2007-0980 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-0980 being exploited?

There is no known exploitation of CVE-2007-0980 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0980 and fix it if it is affected.

What it is: CVE-2007-0980 is a critical authentication bypass vulnerability in n/a, published on 16 Feb 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0980 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-2007-0980/ (Markdown: https://insights.sbomify.com/CVE-2007-0980/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-0980
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-0980
- OSV: https://osv.dev/vulnerability/CVE-2007-0980

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-0980/
Summaries are generated and may contain mistakes; the official description above is the record.