# CVE-2015-0554: Missing authorization in n/a

> Remote attackers can access sensitive information or restart the Pirelli router by directly requesting specific web interface pages without authentication.

- **Severity:** Critical 9.4 (`AV:N/AC:L/Au:N/C:C/I:N/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:** 21 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mrj7-xxw9-838h

## What is CVE-2015-0554?

CVE-2015-0554 is a critical missing authorization vulnerability in n/a, published on 21 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ADB (formerly Pirelli Broadband Solutions) P.DGA4001N router with firmware PDG_TEF_SP_4.06L.6 does not properly restrict access to the web interface, which allows remote attackers to obtain sensitive information or cause a denial of service (device restart) as demonstrated by a direct request to (1) wlsecurity.html or (2) resetrouter.html.

Weakness: CWE-264

## Which versions are affected by CVE-2015-0554?

It affects 1 product.


Products: Adb P.dga4001n Firmware.

## How do I fix CVE-2015-0554?

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

## Is CVE-2015-0554 being exploited?

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

Public exploit code:

- Pirelli ADSL2/2+ Wireless Router P.DGA4001N - Information Disclosure (exploitdb)
- ADB/Pirelli ADSL2/2+ Wireless Router P.DGA4001N - Information Disclosure (nuclei): http/cves/2015/CVE-2015-0554.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0554 and fix it if it is affected.

What it is: CVE-2015-0554 is a critical missing authorization vulnerability in n/a, published on 21 Jan 2015. 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-2015-0554 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-2015-0554/ (Markdown: https://insights.sbomify.com/CVE-2015-0554/index.md)
```

## Sources

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

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