# CVE-2016-4494: Cross-site request forgery in n/a

> Remote attackers can exploit CSRF to hijack authentication and disclose configuration file contents on KMC Controls BAC-5051E devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-prw6-97jx-496v

## What is CVE-2016-4494?

CVE-2016-4494 is a high-severity vulnerability in n/a, published on 10 Jun 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability on KMC Controls BAC-5051E devices with firmware before E0.2.0.2 allows remote attackers to hijack the authentication of unspecified victims for requests that disclose the contents of a configuration file.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Kmc Controls Bac-5051e Firmware.

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

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

## Is CVE-2016-4494 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4495](https://insights.sbomify.com/CVE-2016-4495/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4494 is a high-severity vulnerability in n/a, published on 10 Jun 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-4494 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-4494/ (Markdown: https://insights.sbomify.com/CVE-2016-4494/index.md)
```

## Sources

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

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