A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006.
Noroxi assessment
Priority: Plan (action score 58/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 91.9% (FIRST EPSS); higher than 99.8% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 1, 2019
- Updated
- Jun 16, 2026
- EPSS
- 91.9% · 99th percentile
- CWE
- CWE-918
Report tools
Action score
58
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 28 / 30 · 91.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | axis | cpe:2.3:a:apache:axis |
| oracle | agile engineering data management | cpe:2.3:a:oracle:agile_engineering_data_management |
| oracle | agile product lifecycle management | cpe:2.3:a:oracle:agile_product_lifecycle_management |
| oracle | application testing suite | cpe:2.3:a:oracle:application_testing_suite |
| oracle | big data discovery | cpe:2.3:a:oracle:big_data_discovery |
| oracle | communications asap cartridges | cpe:2.3:a:oracle:communications_asap_cartridges |
| oracle | communications design studio | cpe:2.3:a:oracle:communications_design_studio |
| oracle | communications element manager | cpe:2.3:a:oracle:communications_element_manager |
| oracle | communications network integrity | cpe:2.3:a:oracle:communications_network_integrity |
| oracle | communications order and service management | cpe:2.3:a:oracle:communications_order_and_service_management |
| oracle | communications session report manager | cpe:2.3:a:oracle:communications_session_report_manager |
| oracle | communications session route manager | cpe:2.3:a:oracle:communications_session_route_manager |
and 25 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache axis1.4
- oracle agile engineering data management6.2.1.0
- oracle agile product lifecycle management9.3.3
- oracle application testing suite13.2.0.1
- oracle application testing suite13.3.0.1
- oracle big data discovery1.6
- oracle communications asap cartridges7.2
- oracle communications asap cartridges7.3
- oracle communications design studio7.3.4.3.0
- oracle communications design studio7.3.5.5.0
- oracle communications design studio7.4.0.4.0
- oracle communications design studio7.4.1.1.0
- oracle communications element manager8.0.0
- oracle communications element manager8.1.0
- oracle communications element manager8.1.1
- oracle communications element manager8.2.0
- oracle communications network integrity7.3.5
- oracle communications network integrity7.3.6
- oracle communications order and service management7.3.0.0.0
- oracle communications order and service management7.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Apache Axis 1.4
- Apache Axis 1.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | axis | all versions | — |
| Maven | axis:axis | up to and including 1.4 | — |
| Maven | org.apache.axis:axis | up to and including 1.4 | — |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-40743Apache Axis 1.x (EOL) may allow RCE when untrusted input is passed to getService40Plan
- CVE-2023-51441Apache Axis 1.x (EOL) may allow SSRF when untrusted input is passed to the service admin HTTP API28Monitor
- CVE-2007-2353Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installati28Monitor
- 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
- CVE-2014-3596The 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 C26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2019-04-09 |
| Proof-of-concept repository on GitHub | stars:4 | 2019-10-27 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-05-16 |
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.
- First PoC-23 d
- Published
- TodayOct 16, 2026+2725 d
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.
Credits
All researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0331 · Apr 21, 2021(Oracle Güvenlik Uyarısı Yayınladı)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (11 more)Show less
- lists.apache.org/thread.html/r6d03e45b81eab03580cf7f8bb51cb3e9a1b10a2cc0c6a2d3cc92ed0c%40%3Cannounce.apache.org%3E
- security.netapp.com/advisory/ntap-20240621-0006/
- www.oracle.com/security-alerts/cpuApr2021.html
- www.oracle.com/security-alerts/cpuapr2020.html
- www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.com/security-alerts/cpujan2020.html
- www.oracle.com/security-alerts/cpujan2021.html
- www.oracle.com/security-alerts/cpujul2020.html
- www.oracle.com/security-alerts/cpujul2022.html
- www.oracle.com/security-alerts/cpuoct2021.html
- www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.