GHSA-grw3-hjjm-5cjm CVE-2008-6540
DotNetNuke Default Machine Key Exposure
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 2.48%
- Chance of exploitation in the next 30 days. Higher than 84.55% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-453 Insecure Default Variable Initialization
- Fix
4.8.2- Upgrade DotNetNuke.Core to this version or later
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.
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| DotNetNuke.Core | < 4.8.2 |
4.8.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
DotNetNuke.Core NuGet → 4.8.2
- dotnet
dotnet add package DotNetNuke.Core --version 4.8.2
Weakness
CWE-453: Insecure Default Variable Initialization
The product, by default, initializes an internal variable with an insecure or less secure value than is possible.
How to prevent it
- System Configuration: Disable or change default settings when they can be used to abuse the system. Since those default settings are shipped with the product they are likely to be known by a potential attacker who is familiar with the product. For instance, default credentials should be changed or the associated accounts should be disabled.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2018-18325 Inadequate Encryption Strength in DotNetNuke | High Known exploited | Also affects DotNetNuke.Core |
| CVE-2018-15811 Inadequate Encryption Strength in DotNetNuke | High Known exploited | Also affects DotNetNuke.Core |
| GHSA-x2rg-fmcv-crq5 DNN (aka DotNetNuke) has Remote Code Execution via a cookie | High Known exploited | Also affects DotNetNuke.Core |
| GHSA-fcpv-w245-r2q7 DotNetNuke.Core security code analysis rules triggered | Low | Also affects DotNetNuke.Core |
| GHSA-2rhw-gw3f-477j DNN: Same HostGUID for all new installs | Medium | Also affects DotNetNuke.Core |
| GHSA-fpj4-9qhx-5m6m DNN: Force Friend Request Acceptance | Medium | Also affects DotNetNuke.Core |
| GHSA-ffq7-898w-9jc4 DotNetNuke.Core has stored cross-site-scripting (XSS) via SVG upload | High | Also affects DotNetNuke.Core |
| GHSA-w9pf-h6m6-v89h DotNetNuke.Core Vulnerable to Stored XSS via Module Title | Medium | Also affects DotNetNuke.Core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor