| Package | Affected versions | Patched versions |
|---|---|---|
| com.epam.reportportal:service-api | ≥ 3.1.0, < 4.3.12≥ 5.0.0, < 5.1.1 | 4.3.125.1.1 |
| service-api | ≥ 3.1.0, < 4.3.12≥ 5.0.0, < 5.1.1 | 4.3.125.1.1 |
| Release Date | Affected Projects | Affected Versions | Access Vector | Security Risk |
|---|---|---|---|---|
| Monday, May 4, 2020 | service-api | Every version, starting from 3.1.0 | Remote | Medium |
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 that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
Report Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.
We advise our users install the latest releases we built specifically to address this issue.
Fixed with https://github.com/reportportal/service-api/pull/1201
https://bintray.com/epam/reportportal/service-api/5.1.1 https://bintray.com/epam/reportportal/service-api/4.3.12
docker pull reportportal/service-api:4.3.12docker pull reportportal/service-api:5.1.1The issue was reported to Report Portal Team by an external security researcher. Our Team thanks Julien M. for reporting the issue.
If you have any questions or comments about this advisory email us: [email protected]
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free