CVE-2023-25822
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedReportPortal 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReportPortal's PostgreSQL database uses the ltree extension to store test_item.path for nested test steps. When recursive nesting exceeds ~120 characters in path length, it breaks the path_gist_idx and path_idx indexes, causing database instability and halting test reporting for all but minimal launches.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.2< 5.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ReportPortal Service API versionLocate the service-api package or container image and retrieve its version number. Common locations: Docker image tag, helm chart values, pom.xml dependency, or service startup logs.Affected if Version is below 5.10.0 (or ReportPortal version is below 23.2)
-
Confirm PostgreSQL ltree extension usageQuery the PostgreSQL database: SELECT * FROM pg_extension WHERE extname = 'ltree'; Then verify the test_item table uses an ltree column for path: \d test_item or SELECT column_name, data_type FROM information_schema.columns WHERE table_name = 'test_item';Affected if The ltree extension is installed and test_item.path is of type ltree
-
Check for long nested test pathsQuery the database for path lengths: SELECT id, length(path) as path_length FROM test_item ORDER BY path_length DESC LIMIT 10;Affected if Any test_item records have path length exceeding approximately 120 characters
-
Inspect index status on path columnsRun: SELECT indexname, indexdef FROM pg_indexes WHERE indexname IN ('path_gist_idx', 'path_idx'); Then verify index usability: SELECT * FROM pg_index WHERE indexname IN ('path_gist_idx', 'path_idx');Affected if Indexes are missing, corrupted, or return errors when queried
-
Verify test reporting functionalityAttempt to create a new launch with nested test steps (depth >5 levels) and check if it completes or causes database errors. Also check service logs for PostgreSQL errors related to path or indexes.Affected if Test reporting hangs, fails, or logs show PostgreSQL errors involving path_gist_idx, path_idx, or ltree operations
You are affected if running ReportPortal Service API < 5.10.0 with PostgreSQL ltree extension and have test_item.path values exceeding ~120 characters that have corrupted the path_gist_idx or path_idx indexes, causing test reporting failures.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.10.023.2
Upgrade to com.epam.reportportal:service-api version 5.10.0+ to enable programmatic limiting of nested elements, or delete data with long paths and reindex both indexes as a workaround.
com.epam.reportportal:service-api version 5.10.0 (ReportPortal version 23.2)
- Upgrade the `com.epam.reportportal:service-api` module to version 5.10.0 or later
- Alternatively, upgrade ReportPortal to version 23.2 or later which includes the fixed service-api module
- After upgrade, verify that the maximum number of nested elements is programmatically limited to prevent exceeding the ltree field type indexing limit
- For existing installations with the issue: Delete data with test_item.path length >= 120 (paths exceeding the ltree limit), then reindex both indexes using: REINDEX INDEX path_gist_idx; REINDEX INDEX path_idx;
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25822 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data