CVE-2020-10683

Published May 1, 2020

Last updated 2 months ago

Overview

Description
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.
Source
cve@mitre.org
NVD status
Modified
Products
dom4j, agile_product_lifecycle_management, application_testing_suite, banking_platform, business_process_management_suite, communications_application_session_controller, communications_diameter_signaling_router, communications_unified_inventory_management, data_integrator, documaker, endeca_information_discovery_integrator, enterprise_data_quality, enterprise_manager_base_platform, financial_services_analytical_applications_infrastructure, flexcube_core_banking, fusion_middleware, health_sciences_empirica_signal, health_sciences_information_manager, insurance_policy_administration_j2ee, insurance_rules_palette, jdeveloper, primavera_p6_enterprise_project_portfolio_management, rapid_planning, retail_customer_management_and_segmentation_foundation, retail_integration_bus, retail_order_broker, retail_price_management, retail_xstore_point_of_service, storagetek_tape_analytics_sw_tool, utilities_framework, webcenter_portal, leap, oncommand_api_services, oncommand_workflow_automation, snap_creator_framework, snapcenter, snapmanager, ubuntu_linux

Risk scores

CVSS 3.1

Type
Primary
Base score
9.8
Impact score
5.9
Exploitability score
3.9
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Severity
CRITICAL

CVSS 2.0

Type
Primary
Base score
7.5
Impact score
6.4
Exploitability score
10
Vector string
AV:N/AC:L/Au:N/C:P/I:P/A:P

Weaknesses

nvd@nist.gov
CWE-611

Social media

Hype score
Not currently trending

Configurations

  1. Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.•CVE-2026-84782

References

Sources include official advisories and independent security research.