Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-47578

CRITICAL · 9.1 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Adobe Document Service allows an attacker with administrator privileges to send a crafted request from a vulnerable web application. It is usually used to target internal systems behind firewalls that are normally inaccessible to an attacker from the external network, resulting in a Server-Side Request Forgery vulnerability. On successful exploitation, the attacker can read or modify any file and/or make the entire system unavailable.

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 confidence

Adobe Document Service contains a Server-Side Request Forgery (SSRF) vulnerability allowing an attacker with administrator privileges to send crafted requests from the vulnerable web application. This enables targeting internal systems behind firewalls that would normally be inaccessible, potentially allowing arbitrary file read/write and denial of service.

MitigationRestrict administrator access through least-privilege principles, implement strict input validation and URL allow-listing for outgoing requests, and enforce network segmentation to prevent the service from reaching internal systems.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checks

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

  1. Confirm Adobe Document Service is installed
    Locate the Adobe Document Service installation directory or check for running processes related to Adobe Document Services (such as adobe-dsc, docsc, or similar service names) on the system
    Affected if Adobe Document Service is present on the system
  2. Identify the installed version
    Check the application's version information through its administrative interface, about page, or version file within the installation directory. Compare against any publicly released version numbers for CVE-2024-47578
    Affected if The installed version matches or falls within the affected version range for this CVE
  3. Verify administrator account access
    Review user accounts with administrator-level privileges in the Adobe Document Service admin panel or user management system
    Affected if Administrator accounts exist and are accessible, as this CVE requires administrator privileges to exploit the SSRF vulnerability
  4. Check outgoing request configuration
    Inspect the service configuration files or admin settings for URL validation, allow-listing, or proxy settings that control where outgoing HTTP requests can be sent
    Affected if URL validation or allow-listing is not implemented or is misconfigured, allowing arbitrary URL targets
  5. Audit network accessibility
    Review network firewall rules, routing tables, or access control lists to determine if the Adobe Document Service host can reach internal network segments or internal-only services
    Affected if The service has network access to internal systems behind firewalls that should be restricted

A user is affected if Adobe Document Service is installed, falls within the affected version range, and has administrator accounts that could be leveraged to trigger the SSRF flaw allowing unauthorized internal network access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict administrator access through least-privilege principles, implement strict input validation and URL allow-listing for outgoing requests, and enforce network segmentation to prevent the service from reaching internal systems.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47578 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47578 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