Menu

Star on GitHub · 3.2k

CVE-2014-6172

5.0 · MEDIUM

IBM API Management 3.0 before 3.0.4.0 IF1 allows remote attackers to obtain sensitive analytics information in an encrypted form via unspecified vectors.

Published Jan 21, 2015ibmCWE-200EPSS 2.07%

Overview

CVE-2014-6172 is a medium-severity vulnerability affecting ibm api_management. It was published on January 21, 2015 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

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

Technical description

IBM API Management 3.0 before 3.0.4.0 IF1 allows remote attackers to obtain sensitive analytics information in an encrypted form via unspecified vectors.

Remediation

Check the references section for vendor advisories and patches from ibm. Update api_management 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-6172?

CVE-2014-6172 is a medium-severity vulnerability affecting ibm api_management. It was published on January 21, 2015 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

How severe is CVE-2014-6172?

This vulnerability has a CVSS 2.0 base score of 5.0, 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-6172?

Check the references section for vendor advisories and patches from ibm. Update api_management 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-6172?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2014-6172 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