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

> Remote RTMP servers can execute arbitrary code via the AMF3CD_AddProp function in RTMPDump, requiring users to upgrade the library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8271, GHSA-pfv7-grcx-8gcc, UBUNTU-CVE-2015-8271

## What is CVE-2015-8271?

CVE-2015-8271 is a critical code injection vulnerability in n/a, published on 13 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AMF3CD_AddProp function in amf.c in RTMPDump 2.4 allows remote RTMP Media servers to execute arbitrary code.

Weakness: CWE-123 (Write-what-where Condition)

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

It affects 1 product.


Products: Rtmpdump Project Rtmpdump.

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

Upgrade to a fixed version.

## Is CVE-2015-8271 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8270](https://insights.sbomify.com/CVE-2015-8270/): Null dereference in n/a (high 7.5)
- [CVE-2015-8272](https://insights.sbomify.com/CVE-2015-8272/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8271 is a critical code injection vulnerability in n/a, published on 13 Apr 2017. 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-8271 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-8271/ (Markdown: https://insights.sbomify.com/CVE-2015-8271/index.md)
```

## Sources

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

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