Menu

Star on GitHub · 3.2k

CVE-2014-3629

4.3 · MEDIUM

XML external entity (XXE) vulnerability in the XML Exchange module in Apache Qpid 0.30 allows remote attackers to cause outgoing HTTP connections via a crafted message.

Published Nov 17, 2014apacheCWE-19EPSS 6.92%

Overview

CVE-2014-3629 is a medium-severity vulnerability affecting apache qpid. It was published on November 17, 2014 and has a CVSS 2.0 base score of 4.3 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

XML external entity (XXE) vulnerability in the XML Exchange module in Apache Qpid 0.30 allows remote attackers to cause outgoing HTTP connections via a crafted message.

Remediation

Check the references section for vendor advisories and patches from apache. Update qpid to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2014-3629?

CVE-2014-3629 is a medium-severity vulnerability affecting apache qpid. It was published on November 17, 2014 and has a CVSS 2.0 base score of 4.3 (MEDIUM).

How severe is CVE-2014-3629?

This vulnerability has a CVSS 2.0 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2014-3629?

Check the references section for vendor advisories and patches from apache. Update qpid to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2014-3629?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2014-3629 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2014

View all