# CVE-2014-6031: Memory corruption in n/a

> Remote authenticated administrators can cause a denial of service in F5 BIG-IP systems via a buffer overflow in the mcpq daemon.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8qm4-8v2p-wx57

## What is CVE-2014-6031?

CVE-2014-6031 is a medium-severity memory corruption vulnerability in F5 Big-Ip Access Policy Manager, published on 8 Jun 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Buffer overflow in the mcpq daemon in F5 BIG-IP systems 10.x before 10.2.4 HF12, 11.x before 11.2.1 HF15, 11.3.x, 11.4.x before 11.4.1 HF9, 11.5.x before 11.5.2 HF1, and 11.6.0 before HF4, and Enterprise Manager 2.1.0 through 2.3.0 and 3.x before 3.1.1 HF5 allows remote authenticated administrators to cause a denial of service via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-6031?

It affects 14 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Edge Gateway, F5 Big-Ip Enterprise Manager, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Protocol Security Module, F5 Big-Ip Wan Optimization Manager, F5 Big-Ip Webaccelerator.

## How do I fix CVE-2014-6031?

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

## Is CVE-2014-6031 being exploited?

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

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-6031 and fix it if it is affected.

What it is: CVE-2014-6031 is a medium-severity memory corruption vulnerability in F5 Big-Ip Access Policy Manager, published on 8 Jun 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-6031 in the wild and no public exploit code.

Affected product: F5 Big-Ip Access Policy Manager. 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-2014-6031/ (Markdown: https://insights.sbomify.com/CVE-2014-6031/index.md)
```

## Sources

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

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