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

> Remote attackers can access the admin console without authentication to steal passwords and configuration data from affected IP phones.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gj32-ph9p-h8gc

## What is CVE-2007-0528?

CVE-2007-0528 is a critical authentication bypass vulnerability in n/a, published on 26 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The admin web console implemented by the Centrality Communications (aka Aredfox) PA168 chipset and firmware 1.54 and earlier, as provided by various IP phones, does not require passwords or authentication tokens when using HTTP, which allows remote attackers to connect to existing superuser sessions and obtain sensitive information (passwords and configuration data).

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

It affects 1 product.


Products: Centrality Communications Pa168 Chipset.

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

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

## Is CVE-2007-0528 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0528 exists.

Public exploit code:

- PA168 Chipset IP Phones - Weak Session Management (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0528 is a critical authentication bypass vulnerability in n/a, published on 26 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0528 exists.

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-0528/ (Markdown: https://insights.sbomify.com/CVE-2007-0528/index.md)
```

## Sources

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

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