Skip to content

← Actionable
Unrated

Improper Validation of Certificates in apache axis

CVE-2014-3596GHSA-r53v-vm87-f72c

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Maven axis:axis

    Affected
    <= 1.4
    Fixed in
    no fixed version recorded
  • Maven org.apache.axis:axis

    Affected
    <= 1.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2014-3596: 9.15% estimated exploitation activity in the next 30 days; percentile 95.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-r53v-vm87-f72c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2014-3596

Advisory: Improper Validation of Certificates in apache axis
IDs: CVE-2014-3596, GHSA-r53v-vm87-f72c
Record: https://patchnext.com/advisories/cve-2014-3596 (revision 1, source checked 26 Oct 2026, 16:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven axis:axis: affected <= 1.4
- Maven org.apache.axis:axis: affected <= 1.4

## Suggested inspection (read-only)
- Maven axis:axis: check the installed version with your package manager.
- Maven org.apache.axis:axis: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on axis:axis, org.apache.axis:axis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r53v-vm87-f72c (GitHub-reviewed advisory GHSA-r53v-vm87-f72c lists affected ranges: Maven org.apache.axis:axis >=0 =0 <=1.4)

Commands are suggestions: review each one before running it.

Loading voting…