# CVE-2015-7254: Path traversal in n/a

> Remote attackers can read arbitrary files on Huawei HG532 series routers via directory traversal in icon URIs.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-558f-5537-gq4c

## What is CVE-2015-7254?

CVE-2015-7254 is a medium-severity path traversal vulnerability in n/a, published on 7 Nov 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability on Huawei HG532e, HG532n, and HG532s devices allows remote attackers to read arbitrary files via a .. (dot dot) in an icon/ URI.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 3 products.


Products: Huawei Hg532e, Huawei Hg532n, Huawei Hg532s.

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

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

## Is CVE-2015-7254 being exploited?

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

Public exploit code:

- Huawei Router HG532e - Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7254 is a medium-severity path traversal vulnerability in n/a, published on 7 Nov 2015. 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-2015-7254 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-2015-7254/ (Markdown: https://insights.sbomify.com/CVE-2015-7254/index.md)
```

## Sources

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

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