How severe is CVE-2012-3467?

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

Which packages are affected by CVE-2012-3467?

CVE-2012-3467 affects the following packages: org.apache.qpid:qpid-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-3467?

Update org.apache.qpid:qpid-parent to 0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3467 is resolved across your whole dependency graph.

How do I detect CVE-2012-3467 in my Maven dependencies?

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2012-3467 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-3467 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-3467?

CVE-2012-3467 has an EPSS (Exploit Prediction Scoring System) score of 6.4%, placing it in the 94th 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-2012-3467?

CVE-2012-3467 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-3467 published, and has it been updated?

CVE-2012-3467 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2012-3467 — qpid-parent

CVE-2012-3467 is a Improper Authentication vulnerability in org.apache.qpid:qpid-parent. A fix is available for org.apache.qpid:qpid-parent — see the affected versions and patch details below.

Apache QPID Allows Remote Authentication Bypass

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.qpid:qpid-parent

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

Description

Apache QPID 0.14, 0.16, and earlier uses a NullAuthenticator mechanism to authenticate catch-up shadow connections to AMQP brokers, which allows remote attackers to bypass authentication.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.qpid:qpid-parent`	all versions	0.17`org.apache.qpid:qpid-parent:0.17`

Affected Products

1 product · 4 configurations

Application

qpidapache

≤ 0.16

3 versions

0.50.60.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.qpid:qpid-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.qpid:qpid-parent to 0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3467 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 HatModerate

Product	Fixed in	Advisory
MRG for RHEL-5 v. 2	`mrg-release-0:2.2.0-1.el5`	RHSA-2012:1277
Red Hat Enterprise MRG 2	`mrg-release-0:2.2.0-1.el6`	RHSA-2012:1279

Frequently Asked Questions

Apache QPID 0.14, 0.16, and earlier uses a NullAuthenticator mechanism to authenticate catch-up shadow connections to AMQP brokers, which allows remote attackers to bypass authentication.

O3 Security · Impact-Aware SCA

Is CVE-2012-3467 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works