# CVE-2014-0592: Security feature bypass in n/a

> Remote attackers can bypass security group restrictions in SUSE Cloud by exploiting missing netfilter configuration on bridges during instance creation.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mq43-r7qr-fpq5

## What is CVE-2014-0592?

CVE-2014-0592 is a high-severity vulnerability in n/a, published on 4 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Barclamp (aka barclamp-network) 1.7 for the Crowbar Framework, as used in SUSE Cloud 3, does not enable netfilter on bridges when creating new instances, which allows remote attackers to bypass security group restrictions via unspecified vectors, related to floating IPs.

Weakness: CWE-264

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

It affects 2 products.


Products: Crowbar Barclamp, Novell Suse Cloud.

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

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

## Is CVE-2014-0592 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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