# CVE-2014-8177: Business logic in n/a

> Authenticated users can bypass metadata count limits in Red Hat Gluster Storage Swift by sending multiple crafted requests, violating resource constraints.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8qj2-2gmf-vrgg

## What is CVE-2014-8177?

CVE-2014-8177 is a medium-severity vulnerability in n/a, published on 7 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Red Hat gluster-swift package, as used in Red Hat Gluster Storage (formerly Red Hat Storage Server), allows remote authenticated users to bypass the max_meta_count constraint via multiple crafted requests which exceed the limit when combined.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


Products: Redhat Gluster Storage Management Console, Redhat Gluster Storage Server, Redhat Storage Native Client.

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

Apply the vendor's patch.

## Is CVE-2014-8177 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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