Vulnerability Details CVE-2023-25822
ReportPortal is an AI-powered test automation platform. Prior to version 5.10.0 of the `com.epam.reportportal:service-api` module, corresponding to ReportPortal version 23.2, the 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. The problem was fixed in `com.epam.reportportal:service-api` module version 5.10.0 (product release 23.2), where the maximum number of nested elements were programmatically limited. A workaround is available. After deletion of the data with long paths, and reindexing both indexes (path_gist_idx and path_idx), the database becomes stable and ReportPortal works properly.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.003
EPSS Ranking 52.3%
CVSS Severity
CVSS v3 Score 6.3
Products affected by CVE-2023-25822
-
cpe:2.3:a:reportportal:reportportal:2.7.0
-
cpe:2.3:a:reportportal:reportportal:23.1
-
cpe:2.3:a:reportportal:reportportal:23.1.1
-
cpe:2.3:a:reportportal:reportportal:3.0.0
-
cpe:2.3:a:reportportal:reportportal:3.0.1
-
cpe:2.3:a:reportportal:reportportal:3.0.2
-
cpe:2.3:a:reportportal:reportportal:3.0.5
-
cpe:2.3:a:reportportal:reportportal:3.1.1
-
cpe:2.3:a:reportportal:reportportal:3.2.0
-
cpe:2.3:a:reportportal:reportportal:3.3.0
-
cpe:2.3:a:reportportal:reportportal:3.3.2
-
cpe:2.3:a:reportportal:reportportal:3.3.2-1
-
cpe:2.3:a:reportportal:reportportal:4.0.0
-
cpe:2.3:a:reportportal:reportportal:4.1.0
-
cpe:2.3:a:reportportal:reportportal:4.2.0
-
cpe:2.3:a:reportportal:reportportal:4.3
-
cpe:2.3:a:reportportal:reportportal:5.0.0
-
cpe:2.3:a:reportportal:reportportal:5.1.0
-
cpe:2.3:a:reportportal:reportportal:5.2.0
-
cpe:2.3:a:reportportal:reportportal:5.2.1
-
cpe:2.3:a:reportportal:reportportal:5.2.2
-
cpe:2.3:a:reportportal:reportportal:5.2.3
-
cpe:2.3:a:reportportal:reportportal:5.3.0
-
cpe:2.3:a:reportportal:reportportal:5.3.1
-
cpe:2.3:a:reportportal:reportportal:5.3.2
-
cpe:2.3:a:reportportal:reportportal:5.3.3
-
cpe:2.3:a:reportportal:reportportal:5.3.4
-
cpe:2.3:a:reportportal:reportportal:5.3.5
-
cpe:2.3:a:reportportal:reportportal:5.4.0
-
cpe:2.3:a:reportportal:reportportal:5.5.0
-
cpe:2.3:a:reportportal:reportportal:5.6.0
-
cpe:2.3:a:reportportal:reportportal:5.6.1
-
cpe:2.3:a:reportportal:reportportal:5.6.2
-
cpe:2.3:a:reportportal:reportportal:5.6.3
-
cpe:2.3:a:reportportal:reportportal:5.7.0
-
cpe:2.3:a:reportportal:reportportal:5.7.1
-
cpe:2.3:a:reportportal:reportportal:5.7.2
-
cpe:2.3:a:reportportal:reportportal:5.7.3
-
cpe:2.3:a:reportportal:reportportal:5.7.4
-
cpe:2.3:a:reportportal:service-api:2.6.0
-
cpe:2.3:a:reportportal:service-api:2.7.0
-
cpe:2.3:a:reportportal:service-api:2.7.1
-
cpe:2.3:a:reportportal:service-api:2.7.2
-
cpe:2.3:a:reportportal:service-api:3.0.0
-
cpe:2.3:a:reportportal:service-api:3.0.1
-
cpe:2.3:a:reportportal:service-api:3.1.0
-
cpe:2.3:a:reportportal:service-api:3.1.1
-
cpe:2.3:a:reportportal:service-api:3.2.0
-
cpe:2.3:a:reportportal:service-api:3.2.1
-
cpe:2.3:a:reportportal:service-api:3.3.0
-
cpe:2.3:a:reportportal:service-api:3.3.1
-
cpe:2.3:a:reportportal:service-api:3.3.2
-
cpe:2.3:a:reportportal:service-api:4.0.0
-
cpe:2.3:a:reportportal:service-api:4.1.0
-
cpe:2.3:a:reportportal:service-api:4.1.1
-
cpe:2.3:a:reportportal:service-api:4.2.0
-
cpe:2.3:a:reportportal:service-api:4.2.1
-
cpe:2.3:a:reportportal:service-api:4.3.0
-
cpe:2.3:a:reportportal:service-api:4.3.1
-
cpe:2.3:a:reportportal:service-api:4.3.10
-
cpe:2.3:a:reportportal:service-api:4.3.11
-
cpe:2.3:a:reportportal:service-api:4.3.12
-
cpe:2.3:a:reportportal:service-api:4.3.2
-
cpe:2.3:a:reportportal:service-api:4.3.3
-
cpe:2.3:a:reportportal:service-api:4.3.4
-
cpe:2.3:a:reportportal:service-api:4.3.5
-
cpe:2.3:a:reportportal:service-api:4.3.6
-
cpe:2.3:a:reportportal:service-api:4.3.7
-
cpe:2.3:a:reportportal:service-api:4.3.8
-
cpe:2.3:a:reportportal:service-api:4.3.9
-
cpe:2.3:a:reportportal:service-api:5.0.0
-
cpe:2.3:a:reportportal:service-api:5.1.0
-
cpe:2.3:a:reportportal:service-api:5.1.1
-
cpe:2.3:a:reportportal:service-api:5.2.0
-
cpe:2.3:a:reportportal:service-api:5.2.1
-
cpe:2.3:a:reportportal:service-api:5.2.2
-
cpe:2.3:a:reportportal:service-api:5.2.3
-
cpe:2.3:a:reportportal:service-api:5.3.0
-
cpe:2.3:a:reportportal:service-api:5.3.1
-
cpe:2.3:a:reportportal:service-api:5.3.2
-
cpe:2.3:a:reportportal:service-api:5.3.3
-
cpe:2.3:a:reportportal:service-api:5.3.4
-
cpe:2.3:a:reportportal:service-api:5.3.5
-
cpe:2.3:a:reportportal:service-api:5.4.0
-
cpe:2.3:a:reportportal:service-api:5.5.0
-
cpe:2.3:a:reportportal:service-api:5.5.1
-
cpe:2.3:a:reportportal:service-api:5.6.0
-
cpe:2.3:a:reportportal:service-api:5.6.2
-
cpe:2.3:a:reportportal:service-api:5.6.3
-
cpe:2.3:a:reportportal:service-api:5.7.0
-
cpe:2.3:a:reportportal:service-api:5.7.1
-
cpe:2.3:a:reportportal:service-api:5.7.2
-
cpe:2.3:a:reportportal:service-api:5.7.3
-
cpe:2.3:a:reportportal:service-api:5.7.4
-
cpe:2.3:a:reportportal:service-api:5.8.0
-
cpe:2.3:a:reportportal:service-api:5.9.0
-
cpe:2.3:a:reportportal:service-api:5.9.1
-
cpe:2.3:a:reportportal:service-api:5.9.2