Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions src/conf/security/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,10 @@ An experimental [VEX](https://cyclonedx.org/capabilities/vex/) document is also

👉 [`https://raw.githubusercontent.com/apache/commons-text/refs/heads/master/src/conf/security/VEX.cyclonedx.xml`](VEX.cyclonedx.xml)

It is also available in [OpenVEX format](https://github.com/openvex/spec) at:

👉 [`https://raw.githubusercontent.com/apache/commons-text/refs/heads/master/src/conf/security/openvex.json`](openvex.json)

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

### When is a dependency vulnerability exploitable?
Expand All @@ -59,3 +63,13 @@ Because Apache Commons libraries (including Text) do **not** bundle their depend
* The `analysis` field in the VEX file uses **Markdown** formatting.

For more information about CycloneDX, SBOMs, or VEX, visit [cyclonedx.org](https://cyclonedx.org/).

## Contributing

To add or update a VEX entry:

* Edit the CycloneDX VEX document:
1. Increase the `version` attribute in the `<bom>` element.
2. Update the `timestamp` in the `<metadata>` section.
3. Make your changes to the vulnerability information.
* Regenerate the `openvex.json` file by running the `generate-openvex.sh` script.
25 changes: 17 additions & 8 deletions src/conf/security/VEX.cyclonedx.xml
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,13 @@
To update this document:
1. Increment the `version` attribute in the <bom> element.
2. Update the `timestamp` in the <metadata> section.
3. Regenerate the `openvex.json` file using the `generate-openvex.sh` script.
-->
<bom xmlns="http://cyclonedx.org/schema/bom/1.6"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://cyclonedx.org/schema/bom/1.6 https://cyclonedx.org/schema/bom-1.6.xsd"
serialNumber="urn:uuid:f70dec29-fc7d-41f2-8c60-97e9075e0e73"
version="1">
serialNumber="urn:uuid:9d64577b-0376-4ee7-b154-5ec26a1803f4"
version="2">

<metadata>
<timestamp>2025-07-29T12:26:42Z</timestamp>
Expand All @@ -51,6 +52,10 @@
<vulnerabilities>
<vulnerability>
<id>CVE-2025-48924</id>
<source>
<name>NVD</name>
<url>https://nvd.nist.gov/vuln/detail/CVE-2025-48924</url>
</source>
<references>
<reference>
<id>GHSA-j288-q9x7-2f5v</id>
Expand All @@ -59,20 +64,24 @@
</source>
</reference>
</references>
<recommendation>
Check if untrusted user input is passed to the `StringSubstitutor` or `StringLookup` classes,
and if so, upgrade to Apache Commons Lang 3.18.0 or later.
</recommendation>
<analysis>
<state>exploitable</state>
<responses>
<response>update</response>
</responses>
<detail>
CVE-2025-48924 is exploitable in Apache Commons Text versions 1.5 and later, but only when all the following conditions are met:
CVE-2025-48924 is exploitable in Apache Commons Text versions 1.5 and later, but only when all the following conditions are met:

* The consuming project includes a vulnerable version of Commons Text on the classpath.
As of version `1.14.1`, Commons Text no longer references a vulnerable version of the `commons-lang3` library in its POM file.
* Unvalidated or unsanitized user input is passed to the `StringSubstitutor` or `StringLookup` classes.
* An interpolator lookup created via `StringLookupFactory.interpolatorLookup()` is used.
* The consuming project includes a vulnerable version of Commons Text on the classpath.
As of version `1.14.1`, Commons Text no longer references a vulnerable version of the `commons-lang3` library in its POM file.
* Unvalidated or unsanitized user input is passed to the `StringSubstitutor` or `StringLookup` classes.
* An interpolator lookup created via `StringLookupFactory.interpolatorLookup()` is used.

If these conditions are satisfied, an attacker may cause an infinite loop by submitting a specially crafted input such as `${const:...}`.
If these conditions are satisfied, an attacker may cause an infinite loop by submitting a specially crafted input such as `${const:...}`.
</detail>
<firstIssued>2025-07-29T12:26:42Z</firstIssued>
<lastUpdated>2025-07-29T12:26:42Z</lastUpdated>
Expand Down
177 changes: 177 additions & 0 deletions src/conf/security/generate_openvex.py
Original file line number Diff line number Diff line change
@@ -0,0 +1,177 @@
#!/usr/bin/env python3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ppkarwasz
This seems like a bad idea because all 20+ components will need this duplicated. It seems we should have an "empty" VEX statement for components without issues to affirm that we are OK there. We have TWO plug-ins already for this kind of housekeeping (we really should have a single one), can't we stick stuff like this in there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which plugin do you think would be the best?

As an alternative we can also move the VEX-es into a separate repo, where we can also store the Python scripts to generate them. What do you think? A single repo would also allow us to update VEX entries for all Commons components at once.

Copy link
Member

@garydgregory garydgregory Jul 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about putting this in commons-build-plugin?

That plugin generates files already like the release notes, read me, and some site XML files. This would allow us to also generate the security page with VEX information! Super 👌!

Requiring Python is not great, the plug-in generates files without Python.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I could write a Maven Site Plugin that generates the OpenVEX.

Since it is experimental and might be used by projects other than Commons, I'll write a prototype either in sbom-enforcer or vex-generation-toolset: it will be easier to publish and it can be easier to drop support for it, if it ends up not being useful.

import xml.etree.ElementTree as ET
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is missing its Apache license header which blows up the build's RAT check. Run 'mvn' solo to run the default Maven goal 😉

import json
from datetime import datetime, timezone

NAMESPACES = {
'b': 'http://cyclonedx.org/schema/bom/1.6'
}


def _find_element(parent: ET.Element, tag: str) -> ET.Element | None:
return parent.find(tag, NAMESPACES)


def _find_stripped_text(parent: ET.Element, tag: str) -> str | None:
el = _find_element(parent, tag)
return el.text.strip() if el is not None else None


def _add_optional_date(parent: ET.Element, tag: str, target: dict, key: str) -> None:
el = _find_element(parent, tag)
if el is not None and el.text:
try:
dt = datetime.fromisoformat(el.text.strip()).astimezone(timezone.utc)
target[key] = dt.isoformat().replace('+00:00', 'Z')
except ValueError as e:
raise ValueError(f"Invalid ISO date format in <{tag}>: {el.text}") from e


def load_cyclonedx(path: str = 'VEX.cyclonedx.xml') -> ET.Element:
return ET.parse(path).getroot()


def to_openvex(root: ET.Element) -> dict:
serial_number = root.get('serialNumber')
if not serial_number:
raise ValueError("CycloneDX BOM must have a 'serialNumber' attribute")

version = int(root.get('version', '1'))

result = {
'@context': 'https://openvex.dev/ns/v0.2.0',
'@id': f"https://commons.apache.org/security/vex/{serial_number}",
'author': 'Apache Commons Security Team <security@commons.apache.org>',
'role': 'Security Team',
'version': version,
'tooling': (
"This document was automatically converted from the `VEX.cyclonedx.xml` file.\n"
"Do not edit this file directly, run `generate_openvex.py` to regenerate it."
)
}

_add_optional_date(root, 'b:metadata/b:timestamp', result, 'timestamp')

component = _find_element(root, 'b:metadata/b:component')
if component is None:
raise ValueError("Missing <component> in <metadata>")

product = to_openvex_product(component)

result['statements'] = [
to_openvex_statement(vuln, product)
for vuln in root.findall('.//b:vulnerability', NAMESPACES)
]

return result


def to_openvex_product(component: ET.Element) -> dict:
purl = _find_element(component, 'b:purl')
if purl is None or not purl.text:
raise ValueError("Component must include a non-empty <purl> element")

return {
'@id': purl.text,
'identifiers': {
'purl': purl.text
}
}


def to_openvex_vulnerability(vuln: ET.Element) -> dict:
cdx_id = _find_stripped_text(vuln, 'b:id')
if not cdx_id:
raise ValueError("Vulnerability must have an <id>")

entry = {'name': cdx_id}

source = _find_element(vuln, 'b:source')
if source is not None:
entry['@id'] = _find_stripped_text(source, 'b:url')

entry['aliases'] = [
_find_stripped_text(ref, 'b:id')
for ref in vuln.findall('b:references/b:reference', NAMESPACES)
]

return entry


def to_openvex_statement(vuln: ET.Element, product: dict) -> dict:
analysis = _find_element(vuln, 'b:analysis')
if analysis is None:
raise ValueError("Missing <analysis> in vulnerability")

state = _find_stripped_text(analysis, 'b:state')
if not state:
raise ValueError("Missing <state> in vulnerability analysis")

statement = {
'products': [product],
'vulnerability': to_openvex_vulnerability(vuln),
'status': to_openvex_status(state)
}

justification = _find_stripped_text(analysis, 'b:justification')
if justification:
statement['justification'] = to_openvex_justification(justification)

detail = _find_stripped_text(analysis, 'b:detail')
if detail:
statement['status_notes'] = detail

remediation = _find_stripped_text(vuln, 'b:recommendation')
if remediation:
statement['action_statement'] = remediation
else:
if statement['status'] == 'affected':
raise ValueError("Affected vulnerabilities must have a <recommendation> element")

_add_optional_date(analysis, 'b:firstIssued', statement, 'timestamp')
_add_optional_date(analysis, 'b:lastUpdated', statement, 'last_updated')

return statement


def to_openvex_status(cdx_status: str) -> str:
mapping = {
"resolved": "fixed",
"exploitable": "affected",
"in_triage": "under_investigation",
"false_positive": "not_affected",
"not_affected": "not_affected"
}
status = mapping.get(cdx_status.strip().lower())
if not status:
raise ValueError(f"Unknown CycloneDX status: '{cdx_status}'")
return status


def to_openvex_justification(cdx_justification: str) -> str:
mapping = {
"code_not_present": "vulnerable_code_not_present",
"code_not_reachable": "vulnerable_code_not_in_execute_path",
"requires_configuration": "vulnerable_code_cannot_be_controlled_by_adversary",
"requires_dependency": "component_not_present",
"requires_environment": "vulnerable_code_cannot_be_controlled_by_adversary",
"protected_by_compiler": "inline_mitigations_already_exist",
"protected_at_runtime": "inline_mitigations_already_exist",
"protected_by_mitigating_control": "inline_mitigations_already_exist"
}
result = mapping.get(cdx_justification.strip().lower())
if not result:
raise ValueError(f"Unknown CycloneDX justification: '{cdx_justification}'")
return result


def main():
cyclonedx_root = load_cyclonedx()
openvex_doc = to_openvex(cyclonedx_root)
with open('openvex.json', 'w') as f:
json.dump(openvex_doc, f, indent=2)
print("OpenVEX document written to 'openvex.json'")


if __name__ == "__main__":
main()
33 changes: 33 additions & 0 deletions src/conf/security/openvex.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
{
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://commons.apache.org/security/vex/urn:uuid:9d64577b-0376-4ee7-b154-5ec26a1803f4",
"author": "Apache Commons Security Team <security@commons.apache.org>",
"role": "Security Team",
"version": 2,
"tooling": "This document was automatically converted from the `VEX.cyclonedx.xml` file.\nDo not edit this file directly, run `generate_openvex.py` to regenerate it.",
"timestamp": "2025-07-29T12:26:42Z",
"statements": [
{
"products": [
{
"@id": "pkg:maven/org.apache.commons/commons-text?type=jar",
"identifiers": {
"purl": "pkg:maven/org.apache.commons/commons-text?type=jar"
}
}
],
"vulnerability": {
"name": "CVE-2025-48924",
"@id": "https://nvd.nist.gov/vuln/detail/CVE-2025-48924",
"aliases": [
"GHSA-j288-q9x7-2f5v"
]
},
"status": "affected",
"status_notes": "CVE-2025-48924 is exploitable in Apache Commons Text versions 1.5 and later, but only when all the following conditions are met:\n\n* The consuming project includes a vulnerable version of Commons Text on the classpath.\n As of version `1.14.1`, Commons Text no longer references a vulnerable version of the `commons-lang3` library in its POM file.\n* Unvalidated or unsanitized user input is passed to the `StringSubstitutor` or `StringLookup` classes.\n* An interpolator lookup created via `StringLookupFactory.interpolatorLookup()` is used.\n\nIf these conditions are satisfied, an attacker may cause an infinite loop by submitting a specially crafted input such as `${const:...}`.",
"action_statement": "Check if untrusted user input is passed to the `StringSubstitutor` or `StringLookup` classes,\nand if so, upgrade to Apache Commons Lang 3.18.0 or later.",
"timestamp": "2025-07-29T12:26:42Z",
"last_updated": "2025-07-29T12:26:42Z"
}
]
}
Loading