Oracle Insurance Policy Administration J2EE up to 11.3.0 Architecture xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Oracle Insurance Policy Administration J2EE up to 11.3.0. It has been classified as very critical. The affected element is an unknown function of the component Architecture. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2020-10683. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Oracle Insurance Policy Administration J2EE up to 11.3.0 and classified as very critical. This issue affects an unknown code block of the component Architecture. Using CWE to declare the problem leads to CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Impacted is confidentiality, integrity, and availability.
The weakness was released 01/19/2021 as Oracle Critical Patch Update Advisory - January 2022. The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2020-10683. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/27/2026).
We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 294867 (Oracle Siebel Server <= 25.11 (January 2026 CPU)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (294867). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 294867
Nessus Name: Oracle Siebel Server <= 25.11 (January 2026 CPU)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: github.com
Patch: github.com
Timeline
03/20/2020 🔍01/19/2021 🔍
01/19/2021 🔍
01/19/2022 🔍
08/27/2026 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2022
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-10683 (🔍)
GCVE (CVE): GCVE-0-2020-10683
GCVE (VulDB): GCVE-100-191021
Entry
Created: 01/19/2022 15:48Updated: 08/27/2026 06:18
Changes: 01/19/2022 15:48 (38), 01/24/2022 02:16 (5), 01/24/2022 02:23 (19), 01/22/2026 13:45 (16), 08/27/2026 06:18 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.