CVE-2022-38407
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 InCopy version 17.3 (and earlier) and 16.4.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 confidenceAdobe InCopy versions 17.3 and earlier and 16.4.2 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. An attacker can exploit this by crafting a malicious file that, when opened by a victim, leaks memory information usable to bypass ASLR protection mechanisms.
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>= 16.0, <= 16.4.2>= 17.0, <= 17.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.
-
Check if Adobe InCopy is installedOn Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InCopy or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\InCopy. Alternatively, check for the executable at common installation paths like C:\Program Files\Adobe\Adobe InCopy 2022 or C:\Program Files\Adobe\Adobe InCopy 2023.Affected if The software is present on the system
-
Determine the installed InCopy versionIn Windows Registry, locate the Version value under the InCopy registry key identified in the previous step. Or right-click the InCopy executable in Program Files, select Properties, and view the File version on the Details tab.Affected if A version number is found in the affected range (16.0 to 16.4.2, or 17.0 to 17.3)
-
Confirm the vulnerability is exploitableThe vulnerability triggers when a user opens a specially crafted malicious file. No specific configuration or feature needs to be enabled; the flaw exists in the file parsing logic. Verify the installed version falls within the affected ranges.Affected if The installed version is 16.0 through 16.4.2 inclusive, or 17.0 through 17.3 inclusive
A system is affected if Adobe InCopy version 16.0-16.4.2 or 17.0-17.3 is installed and a user opens a malicious file crafted to trigger the out-of-bounds read.
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 dataApply the vendor patch by updating Adobe InCopy to a version beyond 17.3 and 16.4.2. Until patched, instruct users to avoid opening files from untrusted sources.
- Consultation2.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-38407 — 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-38407 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