Skip to content
Noroxi
CVE-2014-3596· NVD / CVE Program· CNA redhat

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 C

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.

MediumCVSS 5.8 · v2.0—No exploit Fix available
Published
Aug 26, 2014
Updated
Jun 16, 2026
EPSS
9.2% · 95th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
23 / 40 · 5.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.2%

Affected systems

VendorProduct
apacheaxis

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache axisup to 1.4 inclusive
  • apache axis1.0
  • apache axis1.1
  • apache axis1.2
  • apache axis1.2.1
  • apache axis1.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12axisbefore 1.4-211.4-21
Debian:6.0axisbefore 1.4-12+deb6u11.4-12+deb6u1
Mavenaxis:axisup to and including 1.4—
Mavenorg.apache.axis:axisup to and including 1.4—
openSUSE:Leap 15.0axisbefore 1.4-lp150.9.11.4-lp150.9.1
Red Hat:enterprise_linux:5::clientaxisbefore 0:1.2.1-2jpp.8.el5_100:1.2.1-2jpp.8.el5_10
Red Hat:enterprise_linux:5::clientaxis-debuginfobefore 0:1.2.1-2jpp.8.el5_100:1.2.1-2jpp.8.el5_10
Red Hat:enterprise_linux:5::client_workstationaxis-javadocbefore 0:1.2.1-2jpp.8.el5_100:1.2.1-2jpp.8.el5_10
Red Hat:enterprise_linux:5::client_workstationaxis-manualbefore 0:1.2.1-2jpp.8.el5_100:1.2.1-2jpp.8.el5_10
Red Hat:enterprise_linux:6::clientaxisbefore 0:1.2.1-7.5.el6_50:1.2.1-7.5.el6_5
Red Hat:enterprise_linux:6::clientaxis-javadocbefore 0:1.2.1-7.5.el6_50:1.2.1-7.5.el6_5
Red Hat:enterprise_linux:6::clientaxis-manualbefore 0:1.2.1-7.5.el6_50:1.2.1-7.5.el6_5
SUSE:Linux Enterprise Module for Basesystem 15axisbefore 1.4-5.8.11.4-5.8.1
SUSE:Linux Enterprise Server 12 SP3axisbefore 1.4-290.6.11.4-290.6.1

Other highest-scoring records for the same primary product.

  • CVE-2019-0227A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006.
    58Plan
  • CVE-2023-40743Apache Axis 1.x (EOL) may allow RCE when untrusted input is passed to getService
    40Plan
  • CVE-2023-51441Apache Axis 1.x (EOL) may allow SSRF when untrusted input is passed to the service admin HTTP API
    28Monitor
  • CVE-2007-2353Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installati
    28Monitor
  • CVE-2018-8032Apache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services.
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:axis1.4-21 · Debian:12Package registry (OSV)
opensuse:axis1.4-lp150.9.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:axis0:1.2.1-2jpp.8.el5_10 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:axis-debuginfo0:1.2.1-2jpp.8.el5_10 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:axis-javadoc0:1.2.1-2jpp.8.el5_10 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:axis-manual0:1.2.1-2jpp.8.el5_10 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
suse:axis1.4-5.8.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    None

    Weakness class (CWE)

    —

    CVSS vector

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

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    MITRE has no CAPEC/ATT&CK mapping for this CWE.

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records