CVE-2024-55082
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 · uneditedA Server-Side Request Forgery (SSRF) in the endpoint http://{your-server}/url-to-pdf of Stirling-PDF 0.35.1 allows attackers to access sensitive information via a crafted 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 · moderate confidenceServer-Side Request Forgery (SSRF) vulnerability in Stirling-PDF version 0.35.1 at the /url-to-pdf endpoint. The endpoint accepts a user-supplied URL and retrieves content server-side without proper validation, allowing attackers to make the server request internal services, cloud metadata endpoints, or other sensitive resources by providing crafted URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Stirling-PDF installation and versionLocate the Stirling-PDF application in your environment and determine the installed version. Common methods: check the application's about page, examine the JAR/WAR file name, review deployment artifacts, or query the running service for its version information.Affected if Installed version is 0.35.1
-
Verify /url-to-pdf endpoint existsConfirm the /url-to-pdf endpoint is available by accessing it directly or reviewing the application's routing/configuration files that define available endpoints.Affected if The /url-to-pdf endpoint is present and accessible
-
Check network exposure of the endpointDetermine if the Stirling-PDF service is exposed to untrusted networks. Review firewall rules, reverse proxy configuration, and network ACLs that govern who can reach the /url-to-pdf endpoint.Affected if The endpoint is reachable from untrusted networks or the public internet
You are affected if Stirling-PDF version 0.35.1 is running and the /url-to-pdf endpoint is accessible to potentially malicious users.
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.
dbcve · scopedImplement strict URL validation and allowlisting for the /url-to-pdf endpoint. Restrict outgoing network requests to trusted domains and block access to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and cloud metadata endpoints (169.254.169.254).
Stirling-PDF 0.35.2 or later (latest stable release)
- 1. Backup your current Stirling-PDF installation and configuration
- 2. Upgrade Stirling-PDF to version 0.35.2 or later (latest stable release recommended)
- 3. If using Docker, pull the updated image and recreate the container: docker pull stirlingpdf/stirling-pdf:latest followed by recreating the container
- 4. If using JAR deployment, replace the old JAR file with the updated version
- 5. Verify the upgrade by checking that the /url-to-pdf endpoint now properly validates URLs and blocks internal network requests
- 6. Test that legitimate URL-to-PDF functionality still works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-55082 — 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-2024-55082 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