CVE-2021-28805
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 · uneditedInclusion of sensitive information in the source code has been reported to affect certain QNAP switches running QSS. If exploited, this vulnerability allows attackers to read application data. This issue affects: QNAP Systems Inc. QSS versions prior to 1.0.3 build 20210505 on QSW-M2108-2C; versions prior to 1.0.3 build 20210505 on QSW-M2108-2S; versions prior to 1.0.3 build 20210505 on QSW-M2108R-2C; versions prior to 1.0.12 build 20210506 on QSW-M408.
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 confidenceThis is an information disclosure vulnerability in QNAP QSS (QNAP Switch System) firmware where sensitive information is embedded in the source code of the switch software. Attackers can read application data by exploiting this flaw.
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.0.3< 1.0.12CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify your QNAP switch modelCheck the physical device label or log into the QNAP QSS web interface to confirm the exact model number (QSW-M2108-2C, QSW-M2108-2S, QSW-M2108R-2C, or QSW-M408)Affected if The model is one of these four listed models and the firmware version is below the patched build
-
Locate the firmware version in QSS web interfaceLog into the switch web GUI, navigate to System Settings > Firmware Update or similar section, and record the displayed firmware version and build numberAffected if Version shows less than 1.0.3 (for M2108 models) or less than 1.0.12 (for QSW-M408), or build date is before May 2021
-
Check firmware version via CLI if availableAccess the switch command line interface (typically via SSH or console) and run the appropriate version command such as `swversion` or `get system info` to retrieve firmware detailsAffected if Returned version number is below 1.0.3 (M2108 series) or below 1.0.12 (QSW-M408)
-
Compare against affected version rangesFor QSW-M2108-2C, QSW-M2108-2S, and QSW-M2108R-2C: confirm version is below 1.0.3 build 20210505. For QSW-M408: confirm version is below 1.0.12 build 20210506Affected if Any of these models are running firmware versions lower than the specified thresholds
You are affected if you are running a QSW-M2108 series switch below firmware 1.0.3 or a QSW-M408 below firmware 1.0.12, as the vulnerability allows attackers to read sensitive information embedded in the source code.
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 data1.0.31.0.12
Upgrade QSW-M2108-2C, QSW-M2108-2S, and QSW-M2108R-2C to version 1.0.3 build 20210505 or later, and QSW-M408 to version 1.0.12 build 20210506 or later.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28805 — 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-28805 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