CVE-2022-28819
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 · uneditedAdobe Character Animator versions 4.4.2 (and earlier) and 22.3 (and earlier) are 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 SVG 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 confidenceAdobe Character Animator versions 4.4.2 and earlier, and 22.3 and earlier contain an out-of-bounds write vulnerability. Successful exploitation allows arbitrary code execution in the context of the current user, but requires the victim to open a specially crafted malicious SVG 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<= 4.4.2>= 22.0, <= 22.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Character Animator versionOpen Adobe Character Animator and go to Help > About Adobe Character Animator, or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Character Animator\InstallVersion, or on macOS locate the application in /Applications and use Get Info to view the versionAffected if Version cannot be determined or is not visible
-
Compare version against affected rangesIf the version begins with 4.x, verify if it is 4.4.2 or earlier. If the version begins with 22.x, verify if it falls between 22.0 and 22.3 inclusiveAffected if Version is 4.4.2 or lower, OR version is 22.0 through 22.3 inclusive
-
Determine SVG file handling exposureReview whether Adobe Character Animator is used to open or import SVG files from external sources, as exploitation requires the user to open a specially crafted malicious SVG fileAffected if Users open SVG files from untrusted or unknown sources in Adobe Character Animator
System is affected if Adobe Character Animator version is 4.4.2 or earlier, or between 22.0 and 22.3, and users open SVG files in the application.
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 · scopedUpdate Adobe Character Animator to the latest patched version. Avoid opening untrusted or unexpected SVG files from unknown sources.
Adobe Character Animator 22.4 or later (or the next stable release beyond 4.4.2)
- 1. Verify the current installed version of Adobe Character Animator by opening the application and navigating to Help > About Adobe Character Animator
- 2. If the version is 4.4.2 or earlier, OR between 22.0 and 22.3 (inclusive), the installation is vulnerable
- 3. Close Adobe Character Animator completely before updating
- 4. Open Adobe Creative Cloud desktop application
- 5. Navigate to the Apps section and find Adobe Character Animator
- 6. Click the Update button next to Character Animator to install the latest available version
- 7. Alternatively, download the latest version from the Adobe website at adobe.com and run the installer
- 8. After updating, verify the new version number matches a release higher than 22.3 or higher than 4.4.2
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-2022-28819 — 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-2022-28819 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