# CVE-2016-2102: Missing authorization in n/a

> Unauthenticated network access to HAProxy statistics in OpenStack TripleO allows attackers to view sensitive operational data.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8g2x-6frq-q83x, MINI-46qv-jchr-mh5c, MINI-7m7q-5gw6-q5rj, MINI-7rr2-4rqj-8q8g, MINI-7w57-gc4x-6223, MINI-cwvp-6p79-r393, MINI-j9j4-q43j-5gp4

## What is CVE-2016-2102?

CVE-2016-2102 is a medium-severity missing authorization vulnerability in n/a, published on 22 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HAProxy statistics in openstack-tripleo-image-elements are non-authenticated over the network.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Haproxy Haproxy.

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

Apply the vendor's patch.

## Is CVE-2016-2102 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-55203](https://insights.sbomify.com/CVE-2026-55203/): HAProxy - Integer Overflow in FCGI Demux Record Length Field (critical 9.0)
- [CVE-2026-55204](https://insights.sbomify.com/CVE-2026-55204/): HAProxy - NULL Pointer Dereference in hpack_dht_insert Function (high 8.7)
- [CVE-2023-45539](https://insights.sbomify.com/CVE-2023-45539/): Information disclosure in n/a (high 8.2)
- [CVE-2024-45506](https://insights.sbomify.com/CVE-2024-45506/): Denial of service in n/a (high 7.5)
- [CVE-2023-0836](https://insights.sbomify.com/CVE-2023-0836/): Information disclosure in HAProxy (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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