How severe is CVE-2014-9623?

No CVSS score has been assigned to CVE-2014-9623 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-9623?

CVE-2014-9623 affects the following packages: glance (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-9623?

Update glance to 11.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9623 is resolved across your whole dependency graph.

How do I detect CVE-2014-9623 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-9623 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2014-9623 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-9623, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-9623?

CVE-2014-9623 has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-9623?

CVE-2014-9623 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-9623 published, and has it been updated?

CVE-2014-9623 was published on January 23, 2015 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2014-9623 — glance

Fix: openstack/glance@0dc8fbb

CVE-2014-9623 is a CWE-399 vulnerability in glance. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for glance — see the affected versions and patch details below.

OpenStack Glance Bypass the storage quota and Denial of service

Also known asGHSA-j4mh-9wq6-8rg6PYSEC-2026-813

Published

Jan 23, 2015

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍glance

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

OpenStack Glance 2014.2.x through 2014.2.1, 2014.1.3, and earlier allows remote authenticated users to bypass the storage quota and cause a denial of service (disk consumption) by deleting an image in the saving state.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`glance`	all versions	11.0.0a0`pip install --upgrade 'glance==11.0.0a0'`

Affected Products

2 products · 6 configurations

Application

image registry and delivery service \(glance\)openstack

≤ 2014.1.3

1 version

2014.2

Application

openstackredhat

1 version

5.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenStack Glance 2014.2.x through 2014.2.1, 2014.1.3, and earlier allows…

bugs.launchpad.netNVDDec 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update glance to 11.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9623 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-glance-0:2014.1.4-1.el6ost`	RHSA-2015:0838
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-glance-0:2014.1.4-1.el7ost`	RHSA-2015:0837
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-glance-0:2014.2.2-1.el7ost`	RHSA-2015:0644

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-9623 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works