Skip to content

Denial of service vulnerability on creating a Launch with too many recursively nested elements in reportportal

Moderate severity GitHub Reviewed Published Oct 9, 2023 in reportportal/reportportal • Updated Nov 8, 2023

Package

maven com.epam.reportportal:service-api (Maven)

Affected versions

< 5.10.0

Patched versions

5.10.0

Description

Impact

ReportPortal database becomes unstable and reporting almost fully stops except for small launches with approximately 1 test inside when the test_item.path field is exceeded the allowable "ltree" field type indexing limit (path length>=120 approximately, recursive nesting of the nested steps).

REINDEX INDEX path_gist_idx and path_idx aren't helped.

Patches

The problem was fixed in service-api module of version 5.10.0 (product release 23.2), where the maximum number of nested elements were programmatically limited.

Workarounds

After deletion of the data with long paths, and reindexing both indexes (path_gist_idx and path_idx), the database becomes stable and ReportPortal is working properly.

References

@HardNorth HardNorth published to reportportal/reportportal Oct 9, 2023
Published by the National Vulnerability Database Oct 9, 2023
Published to the GitHub Advisory Database Oct 10, 2023
Reviewed Oct 10, 2023
Last updated Nov 8, 2023

Severity

Moderate

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
Low
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:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.217%
(60th percentile)

Weaknesses

CVE ID

CVE-2023-25822

GHSA ID

GHSA-mj24-gpw7-23m9

Source code

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