Skip to content
Fencer Intel
low 3.5

CVE-2012-3371 json

OpenStack Nova Scheduler denial of service through scheduler_hints

published 2012-07-17 14 y ago modified 2026-06-16 4 mo ago also GHSA-xxgm-qpj5-4886 , PYSEC-2012-40 , EUVD-2012-0023

cvss
3.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

The Nova scheduler in OpenStack Compute (Nova) Folsom (2012.2) and Essex (2012.1), when DifferentHostFilter or SameHostFilter is enabled, allows remote authenticated users to cause a denial of service (excessive database lookup calls and server hang) via a request with many repeated IDs in the os:scheduler_hints section.

Patch / fix

  • pypi nova 12.0.0a0
  • nova Debian 14, Debian 13, Debian 12 2012.1.1-5

debian advisories DEBIAN-CVE-2012-3371

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-3371 updated cvss 3.5

OpenStack-Nova: Scheduler denial of service through scheduler_hints

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/openstack/nova/commit/034762e8060dcf0a11cb039b9d426b0d0bb1801d referenced PoC, tagged "exploit" by a source, unverified
  • bugs.launchpad.net https://bugs.launchpad.net/nova/+bug/1017795 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:N/A:P

Affected packages

ecosystem package affected fixed in
pypi nova
<12.0.0a0
12.0.0a0

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.