dbcve.org
FabricApplication · Danielmiessler

CVE-2024-29154

HIGH · 7.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable Zero-click

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
danielmiessler fabric through 1.3.0 allows installer/client/gui/static/js/index.js XSS because of innerHTML mishandling, such as in htmlToPlainText.

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

Cross-site scripting (XSS) vulnerability in danielmiessler fabric through version 1.3.0 in the GUI component (installer/client/gui/static/js/index.js). The htmlToPlainText function improperly handles user-controlled data using innerHTML without sanitization, allowing injection of malicious scripts.

MitigationUpdate fabric to a version beyond 1.3.0 that contains the patched code, or implement proper input sanitization/escaping before using innerHTML in the affected javascript 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
FabricApplication
Affected:<= 1.3.0

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

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. Check installed fabric version
    Run 'fabric --version' or check your package manager for the installed fabric version
    Affected if Version is 1.3.0 or lower (any version <= 1.3.0)
  2. Verify GUI component exists
    Look for the installer/client/gui directory in your fabric installation folder
    Affected if The GUI directory and its static/js/index.js file exist on your system
  3. Inspect vulnerable htmlToPlainText function
    Open installer/client/gui/static/js/index.js and search for the htmlToPlainText function; examine whether it uses innerHTML without sanitization
    Affected if The function uses innerHTML to render user-controlled data without proper sanitization or escaping

You are affected if you are running fabric version 1.3.0 or lower and the GUI component is present with the vulnerable innerHTML pattern in the htmlToPlainText function.

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 1.3.0
Interim mitigation

Update fabric to a version beyond 1.3.0 that contains the patched code, or implement proper input sanitization/escaping before using innerHTML in the affected javascript file.

Recommended fix Moderate confidence

fabric > 1.3.0 (check for 1.3.1 or later release)

  1. 1. Check the latest release of fabric by visiting the official GitHub repository or PyPI page
  2. 2. Upgrade fabric to the latest version using: pip install --upgrade fabric
  3. 3. Verify the version installed: pip show fabric
  4. 4. If using the GUI component, test that the htmlToPlainText function properly sanitizes input
  5. 5. For additional mitigation, ensure the GUI is not exposed to untrusted users or network segments
Caveat Review release notes for any breaking changes between 1.3.0 and the fixed version

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

Fix this in Fabric Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-29154 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