Skip to content

XML Entity Expansion in trytond and proteus

High severity GitHub Reviewed Published Mar 11, 2022 to the GitHub Advisory Database • Updated Feb 3, 2023

Package

pip proteus (pip)

Affected versions

>= 5.0.0, < 5.0.12
>= 6.0.0, < 6.0.5
>= 6.1.0, < 6.2.2

Patched versions

5.0.12
6.0.5
6.2.2
pip trytond (pip)
>= 5.0.0, < 5.0.46
>= 6.0.0, < 6.0.16
>= 6.1.0, < 6.2.6
5.0.46
6.0.16
6.2.6

Description

An XML Entity Expansion (XEE) issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An unauthenticated user can send a crafted XML-RPC message to consume all the resources of the server.

References

Published by the National Vulnerability Database Mar 10, 2022
Published to the GitHub Advisory Database Mar 11, 2022
Reviewed Mar 28, 2022
Last updated Feb 3, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.725%
(81st percentile)

Weaknesses

CVE ID

CVE-2022-26662

GHSA ID

GHSA-pm3h-mm62-pwm8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.