CVE-2024-47446
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 · uneditedAfter Effects versions 23.6.9, 24.6.2 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceOut-of-bounds read vulnerability in Adobe After Effects allows disclosure of sensitive memory contents, which could be leveraged to bypass ASLR mitigation. Exploitation requires a victim to open a malicious After Effects project file.
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<= 23.6.9>= 24.0, < 24.6.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Locate After Effects installationOpen Adobe Creative Cloud desktop app, go to the 'Apps' tab, find Adobe After Effects in the installed software list, or check Program Files/Adobe for the After Effects folderAffected if After Effects is installed on the system
-
Identify installed After Effects versionOpen After Effects, go to Help > About After Effects, or check the version in Adobe Creative Cloud app under the product detailsAffected if Version number is visible and can be compared
-
Compare version against affected rangesIf version is 23.x, check if <= 23.6.9; if version is 24.x, check if < 24.6.3; also check if version is 25.x or higher (not affected based on provided ranges)Affected if Version is 23.6.9 or lower, OR version is 24.0 through 24.6.2 inclusive
-
Determine exposure to malicious project filesCheck if users have ability to open .aep project files from external/untrusted sources; verify email/web download filtering is in place if applicableAffected if Users can open untrusted After Effects project files without additional controls
User is affected if After Effects version is installed within range <=23.6.9 or >=24.0 to <24.6.3, and the application can open project files from untrusted sources.
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 · scoped24.6.3
Apply the Adobe security update when released; until then, enforce user awareness to avoid opening untrusted After Effects project files from unknown sources.
24.6.3 or later
- Open Adobe After Effects and navigate to Help > About Adobe After Effects to check the current version number
- Close any open After Effects instances
- Navigate to the official Adobe website or Creative Cloud desktop application
- Download and install Adobe After Effects version 24.6.3 or later from the official Adobe source
- After installation, verify the version by checking Help > About Adobe After Effects to confirm the installed version is 24.6.3 or higher
- Ensure to only open After Effects project files from trusted sources, as exploitation requires user interaction with malicious files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47446 — 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-47446 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