Skip to content

Harden XML parsing via commons-secure-xml - #393

Draft
ppkarwasz wants to merge 1 commit into
masterfrom
feat/use-commons-xml
Draft

Harden XML parsing via commons-secure-xml#393
ppkarwasz wants to merge 1 commit into
masterfrom
feat/use-commons-xml

Conversation

@ppkarwasz

Copy link
Copy Markdown
Member

Warning

This PR was submitted automatically to smoke-test
Apache Commons Secure XML
and has not yet been verified by a human.
It will stay a draft until a committer reviews it and marks it ready.

Creates XML stream readers, parsers, schema factories and transformers through org.apache.commons:commons-secure-xml (1.0.0-SNAPSHOT until its first release). The secure factories enable XML secure processing and install a non-removable entity-resolver floor: external DTD, entity, schema and XInclude lookups that a caller-set resolver does not resolve are resolved to empty content instead of being fetched, and internal entity expansion is bounded.

  • SCXMLReader goes through SecureXMLInputFactory (the Configuration-supplied XMLResolver still takes precedence, and the factoryId/factoryClassLoader override still selects the underlying implementation), plus SecureSchemaFactory and SecureDocumentBuilderFactory; SCXMLWriter and ContentParser go through SecureTransformerFactory.
  • ContentParser.parseXml now wraps its argument in an InputSource: DocumentBuilder.parse(String) interprets its argument as a URI, so the method never actually parsed the XML content it was documented to parse.
  • CI and CodeQL run with -Puse-apache-snapshots so the SNAPSHOT dependency resolves.

🤖 Generated with Claude Code

Create XML stream readers, parsers, schema factories and transformers
through org.apache.commons:commons-secure-xml. The secure factories
enable FEATURE_SECURE_PROCESSING and install a non-removable
entity-resolver floor on every parser they produce: external DTD,
entity, schema and XInclude lookups that a caller-set resolver does not
resolve are resolved to empty content instead of being fetched, and
internal entity expansion is bounded, regardless of the JAXP
implementation on the classpath.

Changes:
- Add the commons-secure-xml dependency (1.0.0-SNAPSHOT until its first
  release).
- Route factory creation through SecureXMLInputFactory,
  SecureSchemaFactory and SecureDocumentBuilderFactory in SCXMLReader,
  and through SecureTransformerFactory in SCXMLWriter and ContentParser.
  A Configuration-supplied XMLResolver still takes precedence: the floor
  only handles lookups the resolver leaves unresolved, and the
  factoryId/factoryClassLoader override still selects the underlying
  implementation.
- ContentParser.parseXml now wraps its argument in an InputSource:
  DocumentBuilder.parse(String) interprets its argument as a URI, so the
  method never actually parsed the XML content it was documented to
  parse.
- Run the CI and CodeQL builds with -Puse-apache-snapshots (inherited
  from the org.apache:apache parent POM) so the commons-secure-xml
  SNAPSHOT resolves; CodeQL's autobuild receives the profile through
  MAVEN_ARGS.

Assisted-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHgnMnGWHQoH2zD2jFdoMT
@ppkarwasz
ppkarwasz force-pushed the feat/use-commons-xml branch from bb35dc4 to cb9672c Compare August 31, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant