CVE for vulnerability-reports#281

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: Eclipse JGit

Project id: technology.jgit

Request type: publication

Versions affected: [,7.2.0.202503040940-r]

Common Weakness Enumeration:

• {CWE-611: Improper Restriction of XML External Entity Reference}
• {CWE-827: Improper Control of Document Type Definition}

Common Vulnerability Scoring System: {cvss} 3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Summary:

In Eclipse JGit versions 7.2.0.202503040940-r and older, the ManifestParser class used by the repo command and the AmazonS3 class used to implement the experimental amazons3 git transport protocol allowing to store git pack files in an Amazon S3 bucket, are vulnerable to XML External Entity (XXE) attacks when parsing XML files. This vulnerability can lead to information disclosure, denial of service, and other security issues.

Links:

• fixed in JGit 7.2.1.202505142326-r published on Eclipse Nexus and Maven Central

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

mentioned in issue vulnerability-reports#281 (closed)

changed the description

We will use CVE-2025-4949 for this one. It's currently only reserved. As the fix has been already published, should we publish the CVE as well?

added cvereserved label

marked the checklist item All required information is provided as completed

marked the checklist item All required information is provided as incomplete

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

yes, please

In order to published the CVE, can you please translate the CVSS3.1 to CVSS4

Common Vulnerability Scoring System: {cvss} 3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Here is the CVSS4 suggestion: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/S:N/AU:Y/R:U/V:D/RE:L/U:Green

I don't know how to translate CVSS 3.1 to 4

Ok, I'll use the suggestion above

CVE CVE-2025-4949 is published.

added cvepublished label and removed cvereserved label

made the issue visible to everyone

closed

made the issue confidential

made the issue visible to everyone

mentioned in issue eclipsefdn/helpdesk#6323 (closed)