CVE-2017-9822
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 · uneditedDNN (aka DotNetNuke) before 9.1.1 has Remote Code Execution via a cookie, aka "2017-08 (Critical) Possible remote code execution on DNN sites."
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 · moderate confidenceDNN (DotNetNuke) before version 9.1.1 contains an authenticated Remote Code Execution vulnerability where attackers can execute arbitrary code by manipulating specific cookies on the platform.
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< 9.1.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify DNN installation versionCheck the Version.txt file in the website root directory, or examine the web.config file for the version attribute, or log into the Host > Host Settings menu to view the installed version.Affected if The installed version number is lower than 9.1.1 (for example, 9.1.0, 9.0.x, 8.x, 7.x, etc.)
-
Locate DNN version from DLL metadataInspect the DotNetNuke.dll file in the /bin directory using file properties or a tool like ildasm; the assembly version typically matches the product version.Affected if The assembly version shown is below 9.1.1.0.
-
Verify internet-facing exposureDetermine if the DNN site is accessible from the internet by attempting to access the login page or public pages from an external network, or review firewall/networkACL rules allowing inbound HTTP/HTTPS traffic to the server.Affected if The DNN application is directly accessible from untrusted networks without a WAF or authentication proxy.
You are affected if your DNN installation version is any release before 9.1.1 and the site is accessible to unauthenticated users.
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 · scoped9.1.1
Upgrade DNN to version 9.1.1 or later to apply the security patch that addresses this vulnerability.
DNN Platform 9.1.1 or later (current stable release recommended)
- 1. Back up your current DNN installation including database and file system
- 2. Download DNN version 9.1.1 or later from the official DNN repository (github.com/dnnsoftware/dnn-platform)
- 3. Review DNN upgrade documentation for your specific migration path
- 4. Execute the upgrade following standard DNN upgrade procedures
- 5. Verify the upgrade was successful by logging into the DNN portal
- 6. Confirm the DNN version shows 9.1.1 or higher in the Admin > Site Settings area
- 7. Test critical functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9822 — 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-2017-9822 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