tree: 6e39fc643f1aa885fd53775e733bb096a43640f3 [path history] [tgz]
  1. README.md
  2. VEX.cyclonedx.xml
src/conf/security/README.md

CycloneDX Documents for Apache Commons Configuration

The Apache Commons Configuration project publishes multiple CycloneDX documents to help consumers assess the security of their applications using this library:

SBOM (Software Bill of Materials)

Beginning with version 2.9.0, Apache Commons Configuration publishes SBOMs in both XML and JSON formats to Maven Central. These documents describe all components and dependencies of the library, following standard Maven coordinates:

  • Group ID: org.apache.commons
  • Artifact ID: commons-configuration2
  • Classifier: cyclonedx
  • Type: xml or json

Each SBOM lists the library’s required and optional dependencies, helping consumers analyze the software supply chain and manage dependency risk.

[!NOTE] The versions listed in the SBOM reflect the dependencies used during the build and test process for that specific release of Commons Configuration. Your own project may use different versions depending on your dependency management configuration.

VEX (Vulnerability Exploitability eXchange)

An experimental VEX document is also published:

👉 https://raw.githubusercontent.com/apache/commons-configuration/refs/heads/master/src/conf/security/VEX.cyclonedx.xml

This document provides information about the exploitability of known vulnerabilities in the dependencies of Apache Commons Configuration.

When is a dependency vulnerability exploitable?

Because Apache Commons libraries (including Configuration) do not bundle their dependencies, a vulnerability in a dependency is only exploitable if both of the following conditions are true:

  1. The vulnerable dependency is included in the consuming project.
  2. Apache Commons Configuration is explicitly listed as affected by the vulnerability.

Notes and Limitations

  • This VEX document is experimental and provided as-is. The semantics of this document may change in the future.
  • The absence of a vulnerability entry does not indicate that Configuration is unaffected.
  • If a version of Configuration is not listed under the affects section of a vulnerability, that version may still be affected or not.
  • Only the latest major version of Configuration is currently assessed for vulnerabilities.
  • The analysis field in the VEX file uses Markdown formatting.

For more information about CycloneDX, SBOMs, or VEX, visit cyclonedx.org.