AnimateApplication · Adobe

CVE-2022-30664

HIGH · 7.8 CVSS v3.0 Published 2022-06-16
Fix available
A fix is available. Upgrade to after 22.0.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Animate version 22.0.5 (and earlier) is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. 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 confidence

Adobe Animate versions 22.0.5 and earlier contain an out-of-bounds write vulnerability. By convincing a user to open a specially crafted malicious file, an attacker can trigger the vulnerability to achieve arbitrary code execution within the context of the current user's privileges.

MitigationUpdate Adobe Animate to version 22.0.6 or later. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

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
AnimateApplication
Affected:>= 21.0, <= 21.0.10>= 22.0, <= 22.0.5

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/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. Locate Adobe Animate installation path
    On Windows, Adobe Animate is typically installed in C:\Program Files\Adobe\Adobe Animate 2022 or C:\Program Files\Adobe\Adobe Animate 2021. Check both locations for the Animate.exe file.
    Affected if The application is installed in either of these standard paths.
  2. Check installed version via executable properties
    Right-click Animate.exe, select Properties, then go to the Details tab. Note the Product Version and File Version values.
    Affected if The version is displayed in the executable properties.
  3. Compare version against affected ranges
    If the version starts with 21.0, ensure it is greater than 21.0.10. If it starts with 22.0, ensure it is greater than 22.0.5. Versions 21.0.0 through 21.0.10 and 22.0.0 through 22.0.5 are affected.
    Affected if The installed version falls within 21.0.0-21.0.10 or 22.0.0-22.0.5.
  4. Verify application handles untrusted files
    Determine whether users in your environment have the ability or permission to open .FLA or .XFL files received from external sources, as exploitation requires a user to open a specially crafted file.
    Affected if Users can open files from untrusted or external sources within Animate.

You are affected if Adobe Animate version 21.0.0-21.0.10 or 22.0.0-22.0.5 is installed and users can open files from untrusted sources.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 22.0.5
Interim mitigation

Update Adobe Animate to version 22.0.6 or later. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

Recommended fix High confidence

Adobe Animate 22.0.6 or later (or latest 22.x/23.x release)

  1. Open Adobe Creative Cloud desktop application
  2. Navigate to the 'Apps' section
  3. Find Adobe Animate in the list of installed apps
  4. Click the 'Update' button next to Adobe Animate
  5. Wait for the update to download and install
  6. Restart Adobe Animate after the update completes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Animate Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Check whether your project pulls in CVE-2022-30664 — 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-2022-30664 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