CVE-2020-21122: Server-Side Request Forgery in UReport

Summary

20/09/2021
No i
High
Not published

CVE-2020-21122: Server-Side Request Forgery in UReport. Affects com.bstek.ureport:ureport2-console versions < 2.2.9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

UReport is a Maven package that provides a console for designing reports. It is commonly used for generating and managing reports in various applications. The UReport version 2.2.9 is affected by a Server-Side Request Forgery (SSRF) vulnerability on the designer page. This vulnerability allows attackers to detect intranet device ports, potentially leading to unauthorized access or further attacks.

Vulnerability Detail

The SSRF vulnerability in UReport v2.2.9 enables attackers to manipulate the server to make requests to arbitrary URLs, including internal network resources. By exploiting this vulnerability, an attacker can scan for open ports on intranet devices, potentially discovering sensitive services or systems. This can lead to unauthorized access, data leakage, or further compromise of the affected application.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, it is advisable to restrict access to the UReport designer page from untrusted networks or users. Additionally, network-level protections, such as firewalls or Intrusion Detection Systems (IDS), can be implemented to detect and block suspicious requests originating from the affected application.

Conclusion

The SSRF vulnerability in UReport v2.2.9 poses a significant risk to the security of applications utilizing this package. It is crucial to upgrade to a version beyond 2.2.9 to mitigate the risk of SSRF attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.bstek.ureport:ureport2-console →

Share this vulnerability

FAQ

UReport is a Maven package that provides a console for designing reports in various applications.

SSRF is a vulnerability that allows an attacker to manipulate a server to make requests to arbitrary URLs, potentially accessing internal network resources.

The vulnerability in UReport v2.2.9 enables attackers to detect intranet device ports, potentially leading to unauthorized access or further attacks.

To fix this vulnerability, it is recommended to upgrade to a version of UReport that includes a patch for the SSRF vulnerability.

As a temporary workaround, it is advisable to restrict access to the UReport designer page from untrusted networks or users.

Related vulnerabilities

Recent vulnerabilities recorded for com.bstek.ureport:ureport2-console.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback