WhatBrokeToday
GTA 6FAQ
Apache

Apache XML Security for Java XPath Transform Information Disclosure

high

Is it fixed? Not yet.

Ongoing since Nov 17, 17:10 UTC. First reported Nov 17, 17:10 UTC.

What happened

A vulnerability in Apache XML Security for Java incorrectly passes a configuration property when creating specific key elements, allowing potential attackers to use an XPath Transform to extract sensitive information. After updates, file: and http: URIs are only dereferenced when the org.apache.xml.security.allowUnsafeResourceResolving property is set.

What caused it?

Apache XML Security for Java incorrectly passed a configuration property when creating specific key elements, enabling XPath Transform abuse to extract sensitive information.

Source: ubuntu.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    USN-9142-1: Apache XML Security for Java vulnerability

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    USN-9142-1: Apache XML Security for Java vulnerability(opens security advisory in a new tab)

    It was discovered that Apache XML Security for Java incorrectly passed a configuration property when creating specific key elements. An attacker could possibly use this issue to abuse an XPath Transform and extract sensitive information. After this update, file: and http: URIs are only dereferenced when the org.apache.xml.security.allowUnsafeResourceResolving property is set.

    by Ubuntu Security 0upvotes 0comments

FAQ

What happened in the Apache issue?

A vulnerability in Apache XML Security for Java incorrectly passes a configuration property when creating specific key elements, allowing potential attackers to use an XPath Transform to extract sensitive information. After updates, file: and http: URIs are only dereferenced when the org.apache.xml.security.allowUnsafeResourceResolving property is set.

What is affected by the Apache issue?

Apache. Also affected at the same time: Java.

When did the Apache issue start and end?

It started Nov 17, 17:10 UTC and is still ongoing (1 d 11 h so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.