technology.openj9 Fix call to propsfile_read_text buffer length calculation

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.

Basic information

Project name: OpenJ9

Project id: technology.openj9

Request type: publication

Versions affected: [0.8.0,0.49.0]

Common Weakness Enumeration:

• CWE-121: Stack-based Buffer Overflow

Common Vulnerability Scoring System: {cvss} CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N

Summary:

In Eclipse OpenJ9 versions up to 0.51, when used with OpenJDK version 8 a stack based buffer overflow can be caused by modifying a file on disk that is read when the JVM starts.

Links:

• https://github.com/eclipse-openj9/openj9/pull/21762

Tracking

This section will completed by the project team.

• Reserve an entry only
• We're ready for this issue to be reported to the central authority (i.e., make this public now)
• (when applicable) The GitHub Security Advisory is ready to be published now

Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.

This section will be completed by the EMO.

CVE: {cve}

• All required information is provided
• CVE Assigned
• Pushed to Mitre
• Accepted by Mitre

changed the description

changed the description

added cvereserved label

We're going to use CVE-2025-4447 for this.
@pshipton do not forget to update the Tracking section. The presence of a merged PR means the CVE is prepared to be published?

marked the checklist item We're ready for this issue to be reported to the central authority (i.e., make this public now) as completed

Sorry, yes, it's ready to be published.

@tiagolucas will it be published today?

Yes it will.

@tiagolucas any update?

marked the checklist item All required information is provided as completed

marked the checklist item CVE Assigned as completed

The CVE entry was created: https://www.cve.org/cverecord?id=CVE-2025-4447
@pshipton Anything else we can do on this topic?

Thanks, this can be made non confidential and closed.

made the issue visible to everyone

closed