<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Axis2/Java (&lt; 2.0.2) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/axis2/java--2.0.2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 06 Nov 2026 19:23:13 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/axis2/java--2.0.2/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Apache Axis2/Java: SSRF via WS-Addressing endpoints (CVE-2026-123753)</title><link>https://feed.craftedsignal.io/briefs/2026-11-axis2-ssrf/</link><pubDate>Fri, 06 Nov 2026 19:23:13 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-axis2-ssrf/</guid><description>Apache Axis2/Java versions prior to 2.0.2 are vulnerable to unauthenticated SSRF, allowing attackers to force the server to initiate requests to arbitrary network destinations.</description><content:encoded><![CDATA[<p>Apache Axis2/Java versions prior to 2.0.2 are vulnerable to Server-Side Request Forgery (SSRF). An unauthenticated attacker can supply a non-anonymous WS-Addressing 'wsa:ReplyTo' or 'wsa:FaultTo' header, causing the service to initiate a connection to the specified address. This can lead to unauthorized access to internal resources or sensitive network infrastructure.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to perform requests to internal hosts accessible by the Axis2 server, potentially bypassing network segmentation or accessing internal services that do not require authentication.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Apache Axis2/Java to version 2.0.2 or later immediately.</li>
<li>Audit web server and application logs for unusual 'wsa:ReplyTo' or 'wsa:FaultTo' address patterns in SOAP headers.</li>
<li>Restrict egress traffic from the application server to prevent unauthorized internal network access.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache Axis2/Java: Cross-site scripting in OpenAPI module (CVE-2026-123766)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-axis2-xss/</link><pubDate>Fri, 06 Nov 2026 19:23:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-axis2-xss/</guid><description>Apache Axis2/Java version 2.0.1 contains a cross-site scripting (XSS) vulnerability in its OpenAPI module caused by improper sanitization of the Host header.</description><content:encoded><![CDATA[<p>Apache Axis2/Java versions prior to 2.0.2 are vulnerable to cross-site scripting (XSS) within the OpenAPI module. The vulnerability occurs because the Swagger UI page improperly handles the Host header, injecting it into the web page content without sanitization. This allows remote attackers to execute arbitrary scripts in the context of the Axis2 origin.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote attackers to execute arbitrary scripts in the context of the Axis2 origin, potentially leading to session hijacking or unauthorized actions performed by users viewing the affected Swagger UI page.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update Apache Axis2/Java to version 2.0.2 or later to remediate the underlying XSS vulnerability in the OpenAPI module.</li>
<li>As a temporary mitigation, utilize a web application firewall (WAF) to inspect and sanitize the Host header value in incoming requests before they reach the backend application.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item><item><title>Apache Axis2/Java: Unbounded JSON request body memory exhaustion (CVE-2026-120367)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-axis2-json-dos/</link><pubDate>Fri, 06 Nov 2026 19:23:03 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-axis2-json-dos/</guid><description>Apache Axis2/Java versions prior to 2.0.2 are vulnerable to a denial-of-service condition where unauthenticated attackers can exhaust server memory by sending large, unbounded JSON requests.</description><content:encoded><![CDATA[<p>Apache Axis2/Java versions before 2.0.2 contain an &quot;Allocation of Resources Without Limits or Throttling&quot; vulnerability. The JSON message builders, specifically the Gson, Moshi, and HTTP/2 variants, buffer the entire request body into memory without size constraints. An unauthenticated attacker can exploit this behavior by sending a specially crafted, excessively large JSON request to the server, resulting in memory exhaustion and a potential denial-of-service (DoS) condition. Version 2.0.2 introduces configurable limits to mitigate this risk.</p>
<h2 id="impact">Impact</h2>
<p>The primary risk is a denial-of-service condition caused by heap memory exhaustion, which can crash the JVM or cause severe performance degradation for the affected service.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Apache Axis2/Java to version 2.0.2 or later to enable configurable request body size limits.</li>
<li>Implement upstream request size restrictions at the WAF or reverse proxy layer to drop excessively large HTTP POST requests before they reach the Axis2 service.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category></item><item><title>Apache Axis2/Java: Inconsistent enforcement of exposeServiceMetadata (CVE-2026-123779)</title><link>https://feed.craftedsignal.io/briefs/2026-11-axis2-forced-browsing/</link><pubDate>Fri, 06 Nov 2026 19:22:53 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-axis2-forced-browsing/</guid><description>Apache Axis2/Java contains a forced browsing vulnerability where the exposeServiceMetadata parameter is not enforced on specific routes, allowing unauthorized metadata disclosure.</description><content:encoded><![CDATA[<p>Apache Axis2/Java is vulnerable to forced browsing due to inconsistent enforcement of the exposeServiceMetadata configuration parameter. While the parameter is intended to disable metadata exposure, it fails to restrict access to packaged .wsdl and .xsd files, as well as the named-WSDL ?wsdl=NAME route in the standalone HTTP server. This vulnerability allows an attacker to retrieve service metadata even when explicitly disabled.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability may lead to unauthorized information disclosure of internal service configurations and API definitions, potentially aiding further reconnaissance of the target infrastructure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Apache Axis2/Java to version 2.0.2 or later to ensure the exposeServiceMetadata configuration is correctly enforced across all metadata endpoints.</li>
<li>Review public-facing Axis2/Java instances to identify and restrict access to sensitive WSDL and XSD metadata routes until patches are applied.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category></item></channel></rss>