CVE-2020-24444
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 · uneditedAEM Forms SP6 add-on for AEM 6.5.6.0 and Forms add-on package for AEM 6.4 Service Pack 8 Cumulative Fix Pack 2 (6.4.8.2) have a blind Server-Side Request Forgery (SSRF) vulnerability. This vulnerability could be exploited by an unauthenticated attacker to gather information about internal systems that reside on the same network.
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 confidenceA blind Server-Side Request Forgery (SSRF) vulnerability in Adobe Experience Manager (AEM) Forms add-on packages (6.5.6.0 and 6.4.8.2) allows unauthenticated attackers to make the AEM server initiate requests to internal systems, enabling reconnaissance of internal infrastructure without receiving full HTTP responses.
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= 6.4.8.2= 6.5.6.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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.
-
Check AEM Forms add-on package versionNavigate to the AEM Package Manager at /crx/packmgr/index.jsp or use the Felix console at /system/console/bundles to locate installed AEM Forms packages. Look for packages named similar to 'aem-forms' or 'forms-compatibility' and note their exact version numbers.Affected if The installed Forms package version is exactly 6.4.8.2 or exactly 6.5.6.0
-
Verify AEM core versionAccess the AEM system information at /system/console/bundles or check the version.properties file in the crx-quickstart directory. Note the AEM core version (6.4 or 6.5).Affected if AEM core is version 6.4 or 6.5 and the corresponding Forms add-on at the affected versions is installed
-
Confirm Forms feature is enabledCheck if the AEM Forms bundle is in an active state by accessing /system/console/bundles and searching for 'com.adobe.forms' or 'Forms' related bundles. Verify the bundle status is Active.Affected if The Forms bundles are loaded and active, making the SSRF attack surface accessible
-
Check for external network exposureReview the AEM server's network configuration to determine if it has outbound network access. This can be verified by reviewing firewall rules, security groups, or network configuration that allows the AEM server to initiate outbound HTTP connections.Affected if The AEM server has outbound network access, which would allow the SSRF to reach internal infrastructure
You are affected if your AEM Forms add-on package is exactly version 6.4.8.2 or 6.5.6.0 and the Forms bundles are active, enabling unauthenticated attackers to trigger blind SSRF requests from your server.
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 dataApply the Adobe security patch for the affected AEM Forms versions. Additionally, implement network segmentation and egress filtering to restrict outbound connections from the AEM server to internal resources.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24444 — 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-2020-24444 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