# CVE-2015-2252: Code injection in n/a

> Remote attackers can execute arbitrary code with root privileges on Huawei OceanStor UDS devices by uploading a crafted patch containing shell scripts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mj8g-44pc-ghjg

## What is CVE-2015-2252?

CVE-2015-2252 is a high-severity code injection vulnerability in n/a, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Huawei OceanStor UDS devices with software before V100R002C01SPC102 might allow remote attackers to execute arbitrary code with root privileges via a crafted UDS patch with shell scripts.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Huawei Oceanstor Uds Firmware.

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

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

## Is CVE-2015-2252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2254](https://insights.sbomify.com/CVE-2015-2254/): Information disclosure in n/a (critical 9.1)
- [CVE-2015-2251](https://insights.sbomify.com/CVE-2015-2251/): Information disclosure in n/a (high 7.5)
- [CVE-2015-2253](https://insights.sbomify.com/CVE-2015-2253/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2252 is a high-severity code injection vulnerability in n/a, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-2252 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-2252/ (Markdown: https://insights.sbomify.com/CVE-2015-2252/index.md)
```

## Sources

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

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