dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-3432

CRITICAL · 10.0 CVSS v3.1 Published 2023-06-27
Fix available
A fix is available. Upgrade to 1.2023.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
Server-Side Request Forgery (SSRF) in GitHub repository plantuml/plantuml prior to 1.2023.9.

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 confidence

A Server-Side Request Forgery (SSRF) vulnerability in PlantUML versions prior to 1.2023.9 allows remote attackers to make the server perform arbitrary HTTP requests to internal or external resources, potentially exposing internal services and sensitive data.

MitigationUpgrade PlantUML to version 1.2023.9 or later to patch the SSRF vulnerability. Restrict network access from the PlantUML server to internal services as an additional defense-in-depth measure.

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
FedoraOperating system
Affected:= 39
PlantumlApplication
Affected:< 1.2023.9

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PlantUML version
    Run 'plantuml -version' or check your package manager (e.g., 'dnf info plantuml' on Fedora, 'pip show plantuml' if installed via pip, or check the JAR file version if using the standalone version)
    Affected if The version displayed is earlier than 1.2023.9 (e.g., 1.2023.8, 1.2023.7, etc.)
  2. Determine if PlantUML is running as a server
    Check for an active PlantUML server process (look for 'plantuml server', 'java -jar plantuml.jar -server', or check listening ports 8080, 8443, or configured ports). Use 'ps aux | grep plantuml' or 'netstat -tlnp | grep -E "(8080|8443)"'
    Affected if PlantUML is running as a server process and bound to a network-accessible port
  3. Check if the PlantUML server accepts remote requests
    Review the server startup configuration or command line. Look for flags like '-server' without restricting localhost, or check network binding settings in any web server configuration hosting PlantUML
    Affected if The server is bound to 0.0.0.0 or an external interface rather than only localhost (127.0.0.1)
  4. Verify Fedora 39 package version if applicable
    If running on Fedora 39, run 'dnf info plantuml' to see the packaged version. Check the Fedora issue tracker or package repository for the version shipped in Fedora 39
    Affected if The dnf info shows a version earlier than whatever version Fedora backported or ships for 1.2023.9

You are affected if PlantUML version is earlier than 1.2023.9 AND the PlantUML server feature is enabled and accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2023.9 or later
Fixed in 1.2023.9
Vendor patch github.com →
Interim mitigation

Upgrade PlantUML to version 1.2023.9 or later to patch the SSRF vulnerability. Restrict network access from the PlantUML server to internal services as an additional defense-in-depth measure.

Recommended fix High confidence

PlantUML version 1.2023.9 or later

  1. 1. Check the current PlantUML version installed on the system using: `plantuml -version` or `java -jar plantuml.jar -version`
  2. 2. For Fedora 39, update the PlantUML package by running: `sudo dnf update plantuml`
  3. 3. If the package is not available at version 1.2023.9 yet in Fedora repos, download PlantUML version 1.2023.9 or later from the official GitHub releases: https://github.com/plantuml/plantuml/releases
  4. 4. Replace the existing plantuml.jar or binary with the new version
  5. 5. Verify the upgrade was successful by running: `plantuml -version` and confirming it shows version 1.2023.9 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3432 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3432 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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