CVE-2015-7713
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenStack Compute (Nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) do not properly apply security group changes, which allows remote attackers to bypass intended restriction by leveraging an instance that was running when the change was made.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenStack Compute (Nova) fails to apply security group rule changes to instances that were already running at the time the change was made. Instances must be rebooted or rebuilt for new security group rules to take effect, allowing attackers to bypass intended network restrictions by targeting instances that were not restarted after security group modifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2014.2, < 2014.2.4>= 2015.1.0, < 2015.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nova versionRun 'nova-manage version' or check the Nova package version with 'pip show novaclient' or 'rpm -q python-nova' / 'dpkg -l python-nova' depending on your OSAffected if Version is >= 2014.2 and < 2014.2.4, or >= 2015.1.0 and < 2015.1.2
-
List running instancesRun 'nova list --status ACTIVE' to see currently running instancesAffected if There are active instances in the environment
-
Check instance launch timestampsRun 'nova show <instance_id>' for each active instance and note the 'created' timestampAffected if Instances were launched before any security group rule modifications
-
Identify security group modification historyCheck Nova logs for security_group_rule_update events or query the database: 'SELECT id, created_at FROM security_group_rules ORDER BY created_at;'Affected if Security groups were modified after instance launch times
-
Verify active security group membershipRun 'nova show <instance_id>' and check the 'security_groups' field, then compare with current security group rules via 'nova security-group-list'Affected if Running instances may be using stale security group rules from before the most recent modifications
You are affected if Nova version is within the vulnerable range (2014.2.x before 2.4, or 2015.1.x before 1.2) AND you have running instances that were started before security group changes were made.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2014.2.42015.1.2
Restart or rebuild all running instances after making security group changes to ensure new rules are applied, and upgrade Nova to version 2014.2.4 (Juno) or 2015.1.2 (Kilo) or later which contains the fix.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7713 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data