How severe is CVE-2014-3621?

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

Which packages are affected by CVE-2014-3621?

CVE-2014-3621 affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-3621?

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

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

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Yes. There are 1 known exploit references for CVE-2014-3621, 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-3621?

CVE-2014-3621 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th 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-3621?

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

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

CVE-2014-3621 was published on October 2, 2014 and was last updated on July 6, 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-3621 — keystone

Fix: openstack/keystone@2989ff2

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

OpenStack Identity Keystone Exposure of Sensitive Information

Also known asGHSA-8v8f-vc72-pmhcPYSEC-2026-653

Published

Oct 2, 2014

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍keystone

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

The catalog url replacement in OpenStack Identity (Keystone) before 2013.2.3 and 2014.1 before 2014.1.2.1 allows remote authenticated users to read sensitive configuration options via a crafted endpoint, as demonstrated by "$(admin_token)" in the publicurl endpoint field.

Affected Packages

1 total 1 fixed

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

Affected Products

3 products · 5 configurations

ubuntu linuxcanonical

1 version

14.04

Application

keystoneopenstack

≥ 2014.1 && < 2014.1.2.1

range

Application

openstackredhat

2 versions

4.05.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.

The catalog url replacement in OpenStack Identity (Keystone) before 2013…

bugs.launchpad.netNVDJun 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystone to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3621 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatImportant

Product	Fixed in	Advisory
OpenStack 4 for RHEL 6	`openstack-keystone-0:2013.2.4-1.el6ost`	RHSA-2014:1688
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-keystone-0:2014.1.3-2.el6ost`	RHSA-2014:1789
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-keystone-0:2014.1.3-2.el7ost`	RHSA-2014:1790

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3621 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works