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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2023-25822: 0.61% estimated exploitation activity in the next 30 days; percentile 49.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact ReportPortal database becomes unstable and reporting almost fully stops except for small launches with approximately 1 test inside when the testitem.path field is exceeded the allowable "ltree" field type indexing limit (path length=120 approximately, recursive nesting of the nested steps). REINDEX INDEX pathgistidx and pathidx 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 (pathgistidx and pathidx), the database becomes stable and ReportPortal is working properly.

Published by the source

10 Oct 2023, 18:28 UTC

Last modified by the source

8 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:16 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mj24-gpw7-23m9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-25822

Advisory: Denial of service vulnerability on creating a Launch with too many recursively nested elements in reportportal
IDs: CVE-2023-25822, GHSA-mj24-gpw7-23m9
Record: https://patchnext.com/advisories/cve-2023-25822 (revision 1, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.epam.reportportal:service-api 5.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.epam.reportportal:service-api: affected < 5.10.0; fixed in 5.10.0

## Suggested inspection (read-only)
- Maven com.epam.reportportal:service-api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.epam.reportportal:service-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mj24-gpw7-23m9 (GitHub-reviewed advisory GHSA-mj24-gpw7-23m9 lists affected ranges: Maven com.epam.reportportal:service-api >=0 <5.10.0)

Commands are suggestions: review each one before running it.