# CVE-2016-9832: Code injection in n/a

> Remote authenticated users can execute arbitrary code via ABAP injection in PwC ACE-ABAP for SAP Security.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qf6p-46w9-4mmp

## What is CVE-2016-9832?

CVE-2016-9832 is a critical code injection vulnerability in n/a, published on 9 Dec 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PricewaterhouseCoopers (PwC) ACE-ABAP 8.10.304 for SAP Security allows remote authenticated users to conduct ABAP injection attacks and execute arbitrary code via (1) SAPGUI or (2) Internet Communication Framework (ICF) over HTTP or HTTPS, as demonstrated by WEBGUI or Report.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2016-9832?

It affects 1 product.


Products: Pwc Ace-Advanced Business Application Programming.

## How do I fix CVE-2016-9832?

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

## Is CVE-2016-9832 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9832 and fix it if it is affected.

What it is: CVE-2016-9832 is a critical code injection vulnerability in n/a, published on 9 Dec 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-9832 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-2016-9832/ (Markdown: https://insights.sbomify.com/CVE-2016-9832/index.md)
```

## Sources

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

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