Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

OpenStack Nova Router metadata queries are not restricted by tenant

CVE-2013-6419GHSA-22w9-j288-8p9w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nova 12.0.0a0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI nova

    Affected
    < 12.0.0a0
    Fixed in
    12.0.0a0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2013-6419: 1.85% estimated exploitation activity in the next 30 days; percentile 79.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Interaction error in OpenStack Nova and Neutron before Havana 2013.2.1 and icehouse-1 does not validate the instance ID of the tenant making a request, which allows remote tenants to obtain sensitive metadata by spoofing the device ID that is bound to a port, which is not properly handled by (1) api/metadata/handler.py in Nova and (2) the neutron-metadata-agent (agent/metadata/agent.py) in Neutron.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-22w9-j288-8p9w

  2. Revision 1 · created ·

    Published from osv record GHSA-22w9-j288-8p9w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-6419

Advisory: OpenStack Nova Router metadata queries are not restricted by tenant
IDs: CVE-2013-6419, GHSA-22w9-j288-8p9w
Record: https://patchnext.com/advisories/cve-2013-6419 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nova 12.0.0a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected < 12.0.0a0; fixed in 12.0.0a0

## Suggested inspection (read-only)
- `python -m pip show nova`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nova.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-22w9-j288-8p9w (OSV record GHSA-22w9-j288-8p9w lists affected ranges: PyPI nova >=0 <12.0.0a0 (fixed))
- Verified: https://github.com/advisories/GHSA-22w9-j288-8p9w (GitHub-reviewed advisory GHSA-22w9-j288-8p9w lists affected ranges: PyPI nova >=0 <12.0.0a0)

Commands are suggestions: review each one before running it.

Loading voting…