# CVE-2016-4391: Code injection in HP ArcSight WINC Connector

> Remote attackers can execute arbitrary code on HP ArcSight WINC Connector installations, requiring an upgrade to secure the system.

- **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:** No
- **Published:** 6 Aug 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mgw6-g6vp-gh86

## What is CVE-2016-4391?

CVE-2016-4391 is a critical code injection vulnerability in Hewlett Packard Enterprise HP ArcSight WINC Connector, published on 6 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution security vulnerability has been identified in all versions of the HP ArcSight WINC Connector prior to v7.3.0.

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

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

It affects 1 product.


Products: Hp Arcsight Winc Connector.

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

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

## Is CVE-2016-4391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4391 is a critical code injection vulnerability in Hewlett Packard Enterprise HP ArcSight WINC Connector, published on 6 Aug 2018. 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-2016-4391 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HP ArcSight WINC Connector. 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-4391/ (Markdown: https://insights.sbomify.com/CVE-2016-4391/index.md)
```

## Sources

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

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