CVE-2021-29979
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 · uneditedHubs Cloud allows users to download shared content, specifically HTML and JS, which could allow javascript execution in the Hub Cloud instance’s primary hosting domain.*. This vulnerability affects Hubs Cloud < mozillareality/reticulum/1.0.1/20210618012634.
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 confidenceHubs Cloud allows users to download shared content including HTML and JavaScript files without proper sanitization or security headers, enabling stored XSS via malicious scripts that execute when accessed on the primary hosting domain.
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 dataall versionsCVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify Hubs Cloud deploymentCheck for Hubs Cloud services (typically Docker containers with 'hubs', 'reticulum', 'spoke' images) or look for characteristic file paths such as /app/reticulum or environment variables like RETICULUM_VERSIONAffected if Hubs Cloud infrastructure is found in the environment
-
Check Reticulum versionInspect the running Reticulum container or service for version information - typically found in container labels, environment variable RETICULUM_VERSION, or via API endpoint /api/version if availableAffected if Version is earlier than mozillareality/reticulum/1.0.1/20210618012634 or cannot be determined (all versions prior to fix are affected)
-
Verify shared content download feature accessibilityAttempt to access the shared content download endpoint - typically at /api/files/<file_id> or through the Hubs Cloud Admin panel under shared content settingsAffected if Shared content download functionality is enabled and accessible to users
-
Test for missing security headers on downloaded HTML/JS filesUpload a test HTML or JavaScript file via the shared content system, download it via the public URL, and inspect response headers using curl -I - look for missing Content-Disposition: attachment and improper Content-Type headersAffected if Downloaded HTML/JS files lack Content-Type: application/octet-stream or Content-Disposition: attachment headers, or Content-Type is set to text/html/javascript (allowing inline execution)
Environment is affected if running Hubs Cloud with Reticulum version before 1.0.1/20210618012634 AND shared content downloads are accessible AND security headers are not properly applied to HTML/JS file downloads.
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 dataUpgrade to mozillareality/reticulum/1.0.1/20210618012634 or later. Until patched, disable or restrict shared content downloads of HTML/JS files, and ensure proper Content-Type and Content-Disposition headers are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29979 — 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-2021-29979 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