PatchTheCVECVE-2020-10683: dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might e
63
This week
CRITICAL 9.8REMOTEUPGRADEDOWNGRADEDOWNGRADE
CVE-2020-10683 is a critical-severity flaw (CVSS 9.8) affecting dom4j, agile product lifecycle management, application testing suite. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.
Why this priority
- Critical severity
- EPSS top 6%: very likely to be exploited
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 7.3% (top 6%) |
| CISA exploited list | No |
| Weakness | CWE-611 |
| Published | 2020-05-01 |
| Last modified | 2026-08-25 |
Last updated 2026-08-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
dom4j project dom4j UPGRADE
Affected: < 2.0.3 · >= 2.1.0 and < 2.1.3
Fixed in: 2.0.3, 2.1.3
Safe to downgrade to: a release before 2.1.0
1. Check installed version
apt-cache policy dom4j || rpm -q dom4j || dom4j --version
2. UPGRADE to 2.0.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade dom4j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade dom4j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)
apt-cache madison dom4j
sudo apt install dom4j=<VERSION_BEFORE_2.1.0>
sudo apt-mark hold dom4j
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list dom4j
sudo dnf downgrade dom4j-<VERSION_BEFORE_2.1.0>
sudo dnf versionlock add dom4j
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle agile product lifecycle management DOWNGRADE
Affected: 9.3.3 · 9.3.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.3.3
1. Check installed version
apt-cache policy agile-product-lifecycle-management || rpm -q agile-product-lifecycle-management || agile-product-lifecycle-management --version
2. No fixed release: DOWNGRADE to a release before 9.3.3 (Debian / Ubuntu)
apt-cache madison agile-product-lifecycle-management
sudo apt install agile-product-lifecycle-management=<VERSION_BEFORE_9.3.3>
sudo apt-mark hold agile-product-lifecycle-management
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list agile-product-lifecycle-management
sudo dnf downgrade agile-product-lifecycle-management-<VERSION_BEFORE_9.3.3>
sudo dnf versionlock add agile-product-lifecycle-management
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle application testing suite DOWNGRADE
Affected: 13.3.0.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 13.3.0.1
1. Check installed version
apt-cache policy application-testing-suite || rpm -q application-testing-suite || application-testing-suite --version
2. No fixed release: DOWNGRADE to a release before 13.3.0.1 (Debian / Ubuntu)
apt-cache madison application-testing-suite
sudo apt install application-testing-suite=<VERSION_BEFORE_13.3.0.1>
sudo apt-mark hold application-testing-suite
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list application-testing-suite
sudo dnf downgrade application-testing-suite-<VERSION_BEFORE_13.3.0.1>
sudo dnf versionlock add application-testing-suite
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle banking platform UPGRADE
Affected: >= 2.4.0 and <= 2.10.0
Fixed in: newer than 2.10.0
Safe to downgrade to: a release before 2.4.0
1. Check installed version
apt-cache policy banking-platform || rpm -q banking-platform || banking-platform --version
2. UPGRADE to newer than 2.10.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade banking-platform
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade banking-platform
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.4.0 (Debian / Ubuntu)
apt-cache madison banking-platform
sudo apt install banking-platform=<VERSION_BEFORE_2.4.0>
sudo apt-mark hold banking-platform
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list banking-platform
sudo dnf downgrade banking-platform-<VERSION_BEFORE_2.4.0>
sudo dnf versionlock add banking-platform
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle business process management suite DOWNGRADE
Affected: 12.2.1.3.0 · 12.2.1.4.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.2.1.3.0
1. Check installed version
apt-cache policy business-process-management-suite || rpm -q business-process-management-suite || business-process-management-suite --version
2. No fixed release: DOWNGRADE to a release before 12.2.1.3.0 (Debian / Ubuntu)
apt-cache madison business-process-management-suite
sudo apt install business-process-management-suite=<VERSION_BEFORE_12.2.1.3.0>
sudo apt-mark hold business-process-management-suite
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list business-process-management-suite
sudo dnf downgrade business-process-management-suite-<VERSION_BEFORE_12.2.1.3.0>
sudo dnf versionlock add business-process-management-suite
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle communications application session controller DOWNGRADE
Affected: 3.9m0p1
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.9m0p1
1. Check installed version
apt-cache policy communications-application-session-controller || rpm -q communications-application-session-controller || communications-application-session-controller --version
2. No fixed release: DOWNGRADE to a release before 3.9m0p1 (Debian / Ubuntu)
apt-cache madison communications-application-session-controller
sudo apt install communications-application-session-controller=<VERSION_BEFORE_3.9m0p1>
sudo apt-mark hold communications-application-session-controller
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list communications-application-session-controller
sudo dnf downgrade communications-application-session-controller-<VERSION_BEFORE_3.9m0p1>
sudo dnf versionlock add communications-application-session-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-10683?
dom4j: upgrade to 2.0.3, 2.1.3; agile product lifecycle management: downgrade or apply the listed mitigation; application testing suite: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-10683 being exploited?
CVE-2020-10683 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-10683 affect?
CVE-2020-10683 affects dom4j, agile product lifecycle management, application testing suite. Severity is critical (CVSS 9.8). dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavio
How urgent is CVE-2020-10683?
Priority 63/100. Critical severity; EPSS top 6%: very likely to be exploited; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2018-1000632 HIGH 7.5 UPGRADE MITIGATE dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element