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

> Remote attackers can execute arbitrary code in various HPE sizing and planning tools, requiring users to upgrade to patched versions.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 22 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x6p2-2v55-vg8m

## What is CVE-2016-4377?

CVE-2016-4377 is a high-severity code injection vulnerability in n/a, published on 22 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HPE Smart Update in Storage Sizing Tool before 13.0, Converged Infrastructure Solution Sizer Suite (CISSS) before 2.13.1, Power Advisor before 7.8.2, Insight Management Sizer before 16.12.1, Synergy Planning Tool before 3.3, SAP Sizing Tool before 16.12.1, Sizing Tool for SAP Business Suite powered by HANA before 16.11.1, Sizer for ConvergedSystems Virtualization before 16.7.1, Sizer for Microsoft Exchange Server before 16.12.1, Sizer for Microsoft Lync Server 2013 before 16.12.1, Sizer for Microsoft SharePoint 2013 before 16.13.1, Sizer for Microsoft SharePoint 2010 before 16.11.1, and Sizer for Microsoft Skype for Business Server 2015 before 16.5.1 allows remote attackers to execute arbitrary code via unspecified vectors.

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

It affects 15 products.


Products: Hp Converged Infrastructure Solution Sizer Suite, Hp Insight Management Sizer, Hp Power Advisor, Hp Sap Sizing Tool, Hp Sizer for Converged Systems Virtualization, Hp Sizer for Microsoft Exchange Server 2010, Hp Sizer for Microsoft Exchange Server 2013, Hp Sizer for Microsoft Exchange Server 2016, Hp Sizer for Microsoft Lync Server 2013, Hp Sizer for Microsoft Sharepoint 2010, Hp Sizer for Microsoft Sharepoint 2013, Hp Sizer for Microsoft Skype for Business Server 2015, Hp Sizing Tool for Sap Business Suite Powered by Hana, Hp Storage Sizing Tool, Hp Synergy Planning Tool.

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

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

## Is CVE-2016-4377 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4377 is a high-severity code injection vulnerability in n/a, published on 22 Aug 2016. 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-4377 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-4377/ (Markdown: https://insights.sbomify.com/CVE-2016-4377/index.md)
```

## Sources

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

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