Is CVE-2018-15811 exploited in the wild?

Yes. CVE-2018-15811 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2018-15811?

Critical severity, with a CVSS score of 3, published 5 July 2019.

Which products and versions are affected?

DotNetNuke.Core (NuGet) ECOSYSTEM:introduced=9.2.0,fixed=9.2.2.

Is there a fix for CVE-2018-15811?

Yes. DotNetNuke.Core (NuGet): upgrade to 9.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2018-15811 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2018-15811?

Check whether you run Dotnetnuke (Dnn) or DotNetNuke.Core (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2018-15811: Inadequate Encryption Strength in DotNetNuke

CVE-2018-15811 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2019-07-05

DNN (formerly DotNetNuke) versions 9.2 through 9.2.1 utilize a weak encryption algorithm to protect input parameters. This vulnerability can lead to inadequate encryption strength, potentially allowing for unauthorized access to sensitive information or remote code execution via cookie deserialization.

Technologies: Dotnetnuke (Dnn), DotNetNuke.Core (NuGet). Vendors: Dotnetnuke (Dnn), NuGet.

Quick answers

Is CVE-2018-15811 exploited in the wild?: Yes. CVE-2018-15811 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2018-15811?: Critical severity, with a CVSS score of 3, published 5 July 2019.
Which products and versions are affected?: DotNetNuke.Core (NuGet) ECOSYSTEM:introduced=9.2.0,fixed=9.2.2.
Is there a fix for CVE-2018-15811?: Yes. DotNetNuke.Core (NuGet): upgrade to 9.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2018-15811 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2018-15811?: Check whether you run Dotnetnuke (Dnn) or DotNetNuke.Core (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

DotNetNuke.Core (NuGet): upgrade to 9.2.2 or later

dotnet add package DotNetNuke.Core --version 9.2.2

Affected products

DNN Software DotNetNuke (DNN) 9.2 through 9.2.1

Identifiers

CVE-2018-15811
GHSA-h595-8pw6-5q6v

Timeline

2019-07-03: disclosed: NVD Published Date
2020-04-02: other: Public exploit for cookie deserialization RCE released on Packet Storm
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.