Every CVE Search/ Get API key

CVE-2022-46751

Apache Ivy: XML External Entity vulnerability in Apache Ivy

8.2 HighFix available

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
Low

Exploit likelihood

2.00%Up 1.9 points since Aug 21, 2023
90%50%10%1%

What each source reports

NVD Score used 8.2

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
CVE-2022-46751
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Weakness
CWE-91, CWE-611
Updated
2026-11-02
CVE List 8.2

Apache Ivy: XML External Entity vulnerability in Apache Ivy

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
CVE-2022-46751
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Weakness
CWE-611, CWE-91
Updated
2026-11-02
EUVDEUVD-2023-2185 8.2

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
EUVD-2023-2185
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Updated
2026-11-03
GitHub AdvisoriesGHSA-2jc4-r94c-rp7h 8.8

Apache Ivy External Entity Reference vulnerability

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
GHSA-2jc4-r94c-rp7h
CVSS 4.0
8.8 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Weakness
CWE-91, CWE-611
Updated
2026-11-02
OSV 8.2

Apache Ivy: XML External Entity vulnerability in Apache Ivy

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
CVE-2022-46751
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Weakness
CWE-611, CWE-91
Updated
2026-11-02
OSVGHSA-2jc4-r94c-rp7h 8.8

Apache Ivy External Entity Reference vulnerability

Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.

When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.

This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.

Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.

Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".

Record
GHSA-2jc4-r94c-rp7h
CVSS 4.0
8.8 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
CVSS 3.1
8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Weakness
CWE-611, CWE-91
Updated
2026-11-02
Show 4 moreShow less
OSVCLSA-2026-1774398093 No score

TuxCare security update for 25 packages (3 CVEs)

TuxCare rebuilt 25 packages to address 3 CVEs. Fixed in 2.3.0-tuxcare.1.

Record
CLSA-2026-1774398093
Updated
2026-11-02
OSVCLSA-2026-1775608270 No score

TuxCare security update for org.apache.ivy:ivy (2 CVEs)

TuxCare rebuilt org.apache.ivy:ivy to address 2 CVEs. Fixed in 2.3.0-tuxcare.1.

Record
CLSA-2026-1775608270
Updated
2026-11-02
OSVopenSUSE-SU-2024:13148-1 No score

apache-ivy-2.5.2-1.1 on GA media

These are all security issues fixed in the apache-ivy-2.5.2-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2024:13148-1
Updated
2026-11-02
OSVSUSE-SU-2023:4367-1 No score

Security update for apache-ivy

This update for apache-ivy fixes the following issues:

  • Upgrade to version 2.5.2 (bsc#1214422)
  • CVE-2022-46751: Fixed an XML External Entity Injections that could be exploited to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways. (bsc#1214422)
Record
SUSE-SU-2023:4367-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
org.apache.ivy:ivy
Maven
before 2.5.2
2.5.2
org.apache.ivy:ivy
TuxCare:Maven
From an advisory covering 2 CVEs
2.3.0 up to 2.3.0-tuxcare.1
2.3.0-tuxcare.1
org.apache.ivy:ivy
Maven
before 2.5.2, plus listed versions
2.0.02.0.0-beta12.0.0-beta22.0.0-rc12.0.0-rc2
Show 13 moreShow less
2.1.02.1.0-rc12.1.0-rc22.2.02.2.0-rc12.3.02.3.0-rc12.3.0-rc22.4.02.4.0-rc12.5.02.5.0-rc12.5.1
2.5.2
apache-ivy
SUSE:Linux Enterprise Module for Development Tools 15 SP4
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise Module for Development Tools 15 SP5
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise Server 15 SP2-LTSS
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise Server 15 SP3-LTSS
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
Show 6 moreShow less
Affected packages
PackageAffectedFixed
apache-ivy
SUSE:Linux Enterprise Server for SAP Applications 15 SP2
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Linux Enterprise Server for SAP Applications 15 SP3
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
SUSE:Enterprise Storage 7.1
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
openSUSE:Leap 15.4
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
openSUSE:Leap 15.5
before 2.5.2-150200.3.9.1
2.5.2-150200.3.9.1
apache-ivy
openSUSE:Tumbleweed
before 2.5.2-1.1
2.5.2-1.1

History

History
RecordedChangedSources
affected, facts
affected
aliases, publishedEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2022-46751 is a high vulnerability (CVSS 8.2) in Apache Ivy, published August 21, 2023. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.00%, the 80th percentile. Fixed in org.apache.ivy:ivy 2.5.2.

References

Show 7 moreShow less
MoveEnter Open