CVE-2022-29281
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 · uneditedNotable before 1.9.0-beta.8 doesn't effectively prevent the opening of executable files when clicking on a link. There is improper validation of the file URI scheme. A hyperlink to an SMB share could lead to execution of an arbitrary program (or theft of NTLM credentials via an SMB relay attack, because the application resolves UNC paths).
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 confidenceNotable before 1.9.0-beta.8 fails to properly validate file URI schemes in hyperlinks, allowing SMB UNC paths to be processed. When users click links to SMB shares, the application resolves these paths, enabling arbitrary program execution or NTLM credential theft via SMB relay attacks.
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< 1.9.0= 1.9.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Determine Notable application versionOpen Notable and go to Help > About, or check the application executable properties. On Windows, right-click the .exe file and view 'Details' tab for version info. On macOS, right-click the app and select 'Get Info'.Affected if Version is before 1.9.0-beta.8 (any 1.9.0 pre-beta8 or earlier version)
-
Verify hyperlink processing behaviorCreate a note containing a hyperlink with an SMB UNC path format such as 'file:////server/share/file.txt' or '\\server\share\file.txt'. Click the link and observe whether the application attempts to access the SMB resource.Affected if Clicking the link causes Notable to attempt resolving the SMB path (indicating no URI scheme validation)
-
Check for missing file URI scheme validationInspect Notable's behavior when encountering file:// URIs. If hyperlinks with file:// scheme are automatically opened or resolved without blocking, the vulnerability is present.Affected if File URI schemes in hyperlinks are processed/opened without validation (no scheme whitelist or blocking of UNC-style paths)
-
Confirm SMB relay exposureIf the application resolves SMB paths on link click and the user's machine has network access to SMB servers, the system is exposed to NTLM credential theft via SMB relay.Affected if User credentials may be relayed if the application processes SMB UNC paths on link click
A user is affected if their Notable version is before 1.9.0-beta.8 AND clicking hyperlinks containing SMB UNC paths causes the application to attempt resolving those paths.
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 · scoped1.9.0
Upgrade Notable to version 1.9.0-beta.8 or later, which implements proper validation of file URI schemes and blocks SMB UNC path resolution.
Notable 1.9.0 or later
- Upgrade Notable to version 1.9.0 or later (1.9.0-beta.8 or newer contains the fix)
- Test that clicking on SMB/UNC path links in markdown files no longer triggers automatic program execution or credential disclosure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29281 — 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-29281 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