# CVE-2016-4369: Deserialization in n/a

> Remote authenticated attackers can execute arbitrary commands in HPE DDMi via crafted serialized Java objects.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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:** 8 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f597-w4qp-2grh

## What is CVE-2016-4369?

CVE-2016-4369 is a high-severity unsafe deserialization vulnerability in n/a, published on 8 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HPE Discovery and Dependency Mapping Inventory (DDMi) 9.30, 9.31, 9.32, 9.32 update 1, 9.32 update 2, and 9.32 update 3 allows remote authenticated users to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections library.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Hp Discovery and Dependency Mapping Inventory.

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

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

## Is CVE-2016-4369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4369 is a high-severity unsafe deserialization vulnerability in n/a, published on 8 Jun 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-4369 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-4369/ (Markdown: https://insights.sbomify.com/CVE-2016-4369/index.md)
```

## Sources

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

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