Description
DotNetNuke before 4.8.2, during installation or upgrade, does not warn the administrator when the default (1) ValidationKey and (2) DecryptionKey values cannot be modified in the web.config file, which allows remote attackers to bypass intended access restrictions by using the default keys.
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.
Exploit-DB 1
- DotNetNuke 4.8.1 - Default 'ValidationKey' and 'DecriptionKey' Weak Encryption EDB-31465 · remote · Mar 21, 2008 · verified
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| NuGet | DotNetNuke.Core | < 4.8.2 | 4.8.2 | GHSA-grw3-hjjm-5cjm |
References
- dotnetnuke-webconfig-weak-security(41399) vdb-entry
- http://www.dotnetnuke.com/News/SecurityBulletins/SecurityBulletinno12/tabid/1148/Default.aspx
- 28391 vdb-entry
- 29488 third-party-advisory
- 20080321 DotNetNuke Default Machine Key Exposure mailing-list
- 43720 vdb-entry