The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade org.apache.axis2:axis2-kernel to version 2.0.2 or higher.
org.apache.axis2:axis2-kernel is a Web Services / SOAP / WSDL engine, the successor to the widely used Apache Axis SOAP stack.
Affected versions of this package are vulnerable to Forced Browsing of service metadata, because the exposeServiceMetadata parameter is enforced only on the ?wsdl, ?wsdl2, and ?xsd queries in HTTPWorker and ListingAgent. An anonymous caller can read the operation names and the request and response schemas of a service that set exposeServiceMetadata to false by requesting its metadata through an unguarded route, including the packaged .wsdl and .xsd files, the named-WSDL ?wsdl=NAME route of the standalone HTTP server, the services listing, the OpenAPI, Swagger UI and MCP catalog endpoints, WS-MetadataExchange GetMetadata, and the ping module. Only services that disabled exposeServiceMetadata are affected, since a service that leaves metadata exposed is readable by design.
This vulnerability can be avoided by blocking the metadata routes (the /services listing, ?wsdl=NAME, the packaged .wsdl/.xsd paths, the OpenAPI, Swagger UI and MCP endpoints, WS-MetadataExchange and ping) at a fronting reverse proxy, or by undeploying the mex, ping and axis2-openapi modules, for services that must hide their metadata.