CVE-2017-9822 — DotNetNuke.Core
HIGHCVE-2017-9822 is a high-severity (CVSS 8.8) Code Injection vulnerability in DotNetNuke.Core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) and has been used in ransomware campaigns — treat it as actively exploited and patch now. A fix is available for DotNetNuke.Core — see the affected versions and patch details below.
DNN (aka DotNetNuke) has Remote Code Execution via a cookie
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-05-03.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-9822.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2017-9822 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
DotNetNuke.CoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
DNN (aka DotNetNuke) before 9.1.1 has Remote Code Execution via a cookie, aka "2017-08 (Critical) Possible remote code execution on DNN sites."
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | DotNetNuke.Core | all versions | 9.1.1dotnet add package DotNetNuke.Core --version 9.1.1 |
Affected Products
dotnetnukednnsoftwareResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
DotNetNuke - Cookie Deserialization Remote Code Execution (Metasploit)
by Metasploit · Apr 16, 2020
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotNetNuke.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update DotNetNuke.Core to 9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-9822 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
How to detect CVE-2017-9822
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2017-9822 -u https://target- Template
- DotNetNuke 5.0.0 - 9.3.0 - Cookie Deserialization Remote Code Execution
- Severity
- high
- Impact
- Remote code execution through cookie deserialization
- Remediation
- Upgrade DotNetNuke to a version higher than 9.3.0
Template by ProjectDiscovery nuclei-templates (milo2012), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2017-9822 in your dependencies?
Find it across NuGet, including transitive dependencies.