CVE-2024-47445
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 · high confidenceAfter Effects contains an out-of-bounds read vulnerability in versions 23.6.9, 24.6.2 and earlier that allows disclosure of sensitive memory contents, which can be leveraged to bypass ASLR mitigations. Exploitation requires a victim to open a malicious file, making it a user-interaction dependent attack vector.
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.
-
Verify Adobe After Effects is installedCheck for the After Effects application in typical installation locations: Windows: C:\Program Files\Adobe\Adobe After Effects <version>\Support Files\AfterFX.exe or Mac: /Applications/Adobe After Effects <version>/After Effects.appAffected if After Effects is present on the system
-
Determine installed After Effects versionWindows: Right-click AfterFX.exe, select Properties, view Version tab. Alternatively, open After Effects, go to Help > About After Effects to display the full version number. Mac: Right-click After Effects.app, Get Info, or open app and check About After Effects from menu.Affected if Version displayed is 23.6.9 or earlier, or between 24.0 and 24.6.2 inclusive
-
Compare version against affected rangesThe affected version ranges are: 23.x versions up to and including 23.6.9, and version 24.0 through 24.6.2. Any version in these ranges is potentially vulnerable.Affected if Installed version falls within <= 23.6.9 or >= 24.0 but < 24.6.3
-
Review recent file opening activityThe vulnerability requires a victim to open a malicious file. Check system recently opened files or document locations for any untrusted or unexpected After Effects project files (.aep, .aepx) from unknown sources opened around the time of concern.Affected if User has recently opened After Effects project files from untrusted or unknown sources
A system is affected if Adobe After Effects is installed with a version number that is 23.6.9 or earlier, or falls between 24.0 and 24.6.2 inclusive.
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
Update After Effects to the patched version (23.6.9 or later for version 23, 24.6.2 or later for version 24). Avoid opening untrusted or unexpected files from unknown sources.
Adobe After Effects 24.6.3
- 1. Close any running instances of Adobe After Effects
- 2. Open Adobe Creative Cloud desktop application
- 3. Navigate to the 'Apps' section
- 4. Find Adobe After Effects in the list of installed apps
- 5. Click the 'Update' button next to After Effects
- 6. Wait for the update to download and install completely
- 7. Restart your computer if prompted
- 8. Launch After Effects and verify the version is 24.6.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47445 — 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-47445 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