Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-3596

axis: SSL hostname verification bypass, incomplete CVE-2012-5784 fix

Overview

Published
27 Aug 2014
Modified
6 May 2026
Medium CVE
2 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

The getCN function in Apache Axis 1.4 and earlier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5784.

Source: OX vulnerability database

Severity

5.8 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected packages · 2

Packages affected by CVE-2014-3596
EcosystemPackageVulnerableFixed in
Maven axis:axis <=1.4 No fix yet
Maven org.apache.axis:axis <=1.4 No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

debian 4 releases · 1 package

fixed 4
axis
debian fixes for CVE-2014-3596
ReleasePackageFixed in
11 axis 1.4-21
12 axis 1.4-21
13 axis 1.4-21
14 axis 1.4-21

echo 1 release · 1 package

fixed 1
axis
echo fixes for CVE-2014-3596
ReleasePackageFixed in
axis 1.4-21

openSUSE 1 release · 1 package

fixed 1
axis
openSUSE fixes for CVE-2014-3596
ReleasePackageFixed inAdvisory
Tumbleweed axis +1 1.4-302.6 openSUSE-SU-2024:10646-1

References

Show all 31 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.