Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2019-0227

HIGH

CVE-2019-0227 is a high-severity (CVSS 7.5) vulnerability in org.apache.axis:axis. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2019-0227 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Server Side Request Forgery in Apache Axis

Also known asGHSA-h9gj-rqrw-x4fq
Published
May 1, 2019
Updated
Mar 15, 2026
Affected
2 pkgs
Patched
None yet
Exploits
4 known

EPSS Exploitation Probability

via FIRST.org ↗
91.9%probability of exploitation in next 30 days
Very High Risk100th percentile+5.44%
84.9%87.8%90.7%93.6%89.2%91.9%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
org.apache.axis:axisaxis:axis

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.axis:axisall versionsNo fix
Mavenaxis:axisall versionsNo fix
Exploits & PoCs
4

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46682remotemultiple

Apache Axis 1.4 - Remote Code Execution

by David Yesland · Apr 9, 2019

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.axis:axis. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of org.apache.axis:axis has shipped for CVE-2019-0227 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2019-0227 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2019-0227. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.
O3 Security · Impact-Aware SCA

Is CVE-2019-0227 in your dependencies?

O3 detects CVE-2019-0227 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.