CVE-2022-27873
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 · uneditedAn attacker can force the victim’s device to perform arbitrary HTTP requests in WAN through a malicious SVG file being parsed by Autodesk Fusion 360’s document parser. The vulnerability exists in the application’s ‘Insert SVG’ procedure. An attacker can also leverage this vulnerability to obtain victim’s public IP and possibly other sensitive information.
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 malicious SVG file parsed by Autodesk Fusion 360's document parser through the 'Insert SVG' feature allows an attacker to force the victim's device to make arbitrary HTTP requests to WAN addresses. This SSRF-like behavior enables attackers to discover the victim's public IP address and potentially exfiltrate sensitive information by routing requests through the victim's machine.
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<= 2.0.12887CVSS 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.1/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.
-
Verify Fusion 360 version numberOpen Fusion 360, then access Help > About Autodesk Fusion 360 (or check the application title bar/version info in Settings). Record the full version string displayed.Affected if The displayed version is 2.0.12887 or any version lower than 2.0.12887 (e.g., 2.0.12000, 1.0.xxxx). Compare your version against the affected range: <= 2.0.12887.
-
Confirm Insert SVG feature is availableIn the Fusion 360 interface, navigate to the Insert tab or menu and look for an option labeled 'SVG', 'Insert SVG', or 'Import SVG'. Alternatively, search for SVG in the application's search or help function.Affected if The Insert SVG feature is present and accessible in the application, indicating the vulnerable code path could be triggered.
-
Check for recent SVG file importsReview your recent documents or design files for any .svg files that may have been imported or inserted into Fusion 360 projects. Check the design timeline or file browser for SVG references.Affected if You have recently opened, imported, or inserted untrusted SVG files into Fusion 360 designs, which could have triggered the vulnerability.
You are affected if your installed Fusion 360 version is 2.0.12887 or earlier AND the Insert SVG feature is accessible in your installation.
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 dataOrganizations should disable or restrict the 'Insert SVG' feature in Fusion 360 until Autodesk releases an official patch. Users should avoid opening untrusted or unexpected SVG files in Fusion 360.
- Consultation2.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-27873 — 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-27873 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