XXE (XML External Entity) in com.epam.reportportal:service-api (CVE-2021-29620)
Summary
Vulnerability in com.epam.reportportal:service-api (CVE-2021-29620). Confidential information can be exposed externally. Mitigation: upgrade to 5.4.0 or later.
Original description
The description as published by the source.
Impact
Starting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file which imports external Document Type Definition (DTD) file with external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
Patches
Fixed with: https://github.com/reportportal/service-api/pull/1392
Binaries
docker pull reportportal/service-api:5.4.0
https://github.com/reportportal/service-api/packages/846871?version=5.4.0
For more information
If you have any questions or comments about this advisory email us: support@reportportal.io
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29620 has been found in com.epam.reportportal:service-api.
Confidential information can be exposed externally.
What to do: upgrade com.epam.reportportal:service-api to 5.4.0 or later.
If unsure, ask your IT team or search "com.epam.reportportal:service-api CVE-2021-29620" on the vendor's site.
CVE-2021-29620 (com.epam.reportportal:service-api) — CWE-611
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-611) exists in com.epam.reportportal:service-api.
Check the vendor advisory for the affected versions of com.epam.reportportal:service-api.
Severity: ?. Confidential information can be exposed externally.
Update to 5.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.epam.reportportal:service-api を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.epam.reportportal:service-api to 5.4.0ステージング環境で 5.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web mvnrepository.com