dbcve.org
FedoraOperating system · Fedoraproject

CVE-2013-2014

MEDIUM · 5.0 CVSS v2.0 Published 2014-06-02
Fix available
A fix is available. Upgrade to 2013.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
OpenStack Identity (Keystone) before 2013.1 allows remote attackers to cause a denial of service (memory consumption and crash) via multiple long requests.

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 confidence

OpenStack Identity (Keystone) versions before 2013.1 contain a denial of service vulnerability where remote attackers can send multiple long requests to consume excessive memory, eventually causing the service to crash.

MitigationUpgrade Keystone to version 2013.1 or later. If immediate upgrade is not possible, implement rate limiting on the API endpoints to restrict the number of requests per client and monitor for unusual memory consumption patterns.

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
FedoraOperating system
Affected:= 19
KeystoneApplication
Affected:>= 2013, < 2013.1

CVSS 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
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Keystone is installed
    Check for keystone package or service: rpm -qa | grep keystone or systemctl list-units | grep keystone
    Affected if Keystone package or service is found on the system
  2. Confirm Fedora 19 is the operating system
    Run: cat /etc/fedora-release or cat /etc/redhat-release
    Affected if Operating system is Fedora 19
  3. Check Keystone package version
    Run: rpm -q keystone or pip show keystone
    Affected if Version is 2013.x (any subversion before 2013.1)
  4. Verify API service is network-accessible
    Check keystone configuration files (typically /etc/keystone/keystone.conf) for bind_host and bind_port settings, or check if port 5000/35357 is listening
    Affected if Keystone API is bound to a reachable network address and port is open

A system is affected if it runs Keystone version 2013.x (before 2013.1) on Fedora 19 with the API network-accessible, allowing remote attackers to send long requests that exhaust memory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2013.1 or later
Fixed in 2013.1
Interim mitigation

Upgrade Keystone to version 2013.1 or later. If immediate upgrade is not possible, implement rate limiting on the API endpoints to restrict the number of requests per client and monitor for unusual memory consumption patterns.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2014 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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