← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2018-15811 exploited? Yes: in CISA KEV since 3 Nov 2021

Gociux · DotNetNuke (DNN) · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2018-15811, DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 3 Nov 2021, 854 days after it was published. It affects DotNetNuke (DNN). If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 3 Nov 2021
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity7.5CVSS 3.1 · high
US federal due3 May 2022BOD 22-01 deadline

What it is

DotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters.

VendorDotNetNuke (DNN) (3 exploited CVEs in KEV)
ProductDotNetNuke (DNN)
VulnerabilityDotNetNuke (DNN) Inadequate Encryption Strength Vulnerability
WeaknessCWE-326
Published3 Jul 2019
Added to KEV3 Nov 2021
Reported by (CNA)mitre

What to do

  1. Check whether you run it. Look for DotNetNuke (DNN) in your asset inventory, including appliances and cloud images. Stack check lists every exploited DotNetNuke (DNN) CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 3 Jul 2019.
  4. Get told next time. Email alerts when CISA adds a CVE for DotNetNuke (DNN).

Other exploited CVEs in DotNetNuke (DNN)

References

Questions

Is CVE-2018-15811 being exploited?

Yes. CISA added CVE-2018-15811 to the Known Exploited Vulnerabilities catalog on 3 Nov 2021, which means there is reliable evidence of exploitation in the wild.

Is CVE-2018-15811 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2018-15811?

Apply updates per vendor instructions. Check DotNetNuke (DNN)'s advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected DotNetNuke (DNN) and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in November 2021 · DotNetNuke (DNN) scorecard · act-now radar.

Running DotNetNuke (DNN) in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →