CVE-2023-50090
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 · uneditedArbitrary File Write vulnerability in the saveReportFile method of ureport2 2.2.9 and before allows attackers to write arbitrary files and run arbitrary commands via crafted POST request.
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 confidenceArbitrary File Write vulnerability in ureport2's saveReportFile method allows authenticated or unauthenticated attackers to write arbitrary files to the filesystem via a crafted POST request, potentially leading to remote code execution.
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<= 2.2.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 ureport2 installation and versionLocate the ureport2 JAR file or library in your application (typically named ureport2-core.jar, ureport2-*.jar). Check the filename or MANIFEST.MF inside the JAR for the version number. Alternatively, search your project dependencies (Maven pom.xml, Gradle build.gradle) for ureport2 and note the declared version.Affected if The installed ureport2 version is 2.2.9 or lower.
-
Verify the saveReportFile endpoint existsSearch your application codebase or WAR file for the string 'saveReportFile' to confirm the vulnerable method exists in your deployment. Check REST controller mappings that expose this endpoint (typically under /ureport or /api/ureport paths).Affected if The saveReportFile method is present in your deployed ureport2 instance.
-
Check endpoint accessibility without authenticationAttempt a POST request to the suspected saveReportFile endpoint (often /ureport/saveReportFile or similar) without providing credentials. Observe if the application accepts the request or returns an authentication error.Affected if The endpoint responds without requiring authentication or valid session credentials.
-
Inspect file write parameters in requestsReview the saveReportFile method implementation to confirm it accepts a filename or path parameter from the request body without proper sanitization. Look for file path construction using user-supplied input.Affected if The method uses unsanitized user input to determine the target file path for writing.
You are affected if ureport2 version 2.2.9 or lower is deployed AND the saveReportFile endpoint is accessible without proper authentication or input validation.
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.
From vendor dataUpgrade to a patched version of ureport2 if available; otherwise, disable or restrict access to the saveReportFile endpoint and implement strict input validation with path sanitization to prevent directory traversal and enforce allowed file paths.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50090 — 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-50090 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