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

> Remote attackers can bypass access restrictions because the firewall is disabled when the OVS monolithic plug-in is not used.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 2 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-47pg-jr9r-j5r6, RHSA-2014:1691

## What is CVE-2014-3703?

CVE-2014-3703 is a medium-severity vulnerability in n/a, published on 2 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenStack PackStack 2012.2.1, when the Open vSwitch (OVS) monolithic plug-in is not used, does not properly set the libvirt_vif_driver configuration option when generating the nova.conf configuration, which causes the firewall to be disabled and allows remote attackers to bypass intended access restrictions.

Weakness: CWE-264

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-packstack` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.1-0.33.dev1048.el6ost |
| `openstack-packstack-doc` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.1-0.33.dev1048.el6ost |
| `openstack-packstack-puppet` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.1-0.33.dev1048.el6ost |

Products: Redhat Packstack.

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

Apply the vendor's patch.

## Is CVE-2014-3703 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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