CVE-2019-10641: Contao Does Not Invalidate Existing Sessions When Password Changes

Quick answers

Is CVE-2019-10641 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-10641 being exploited in the wild.

How severe is CVE-2019-10641?

Low severity, with a CVSS score of 3, published 14 May 2022.

Which products and versions are affected?

contao/contao (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.37; contao/core (Packagist) ECOSYSTEM:introduced=3.0.0,fixed=3.5.39; contao/core-bundle (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.37.

Is there a fix for CVE-2019-10641?

Yes. contao/contao (Packagist): upgrade to 4.4.37 or later; contao/core (Packagist): upgrade to 3.5.39 or later; contao/core-bundle (Packagist): upgrade to 4.4.37 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2019-10641?

Check whether you run contao/contao (Packagist), contao/core (Packagist) or contao/core-bundle (Packagist) 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

• contao/contao (Packagist): upgrade to 4.4.37 or later

  composer require contao/contao:^4.4.37

• contao/core (Packagist): upgrade to 3.5.39 or later

  composer require contao/core:^3.5.39

• contao/core-bundle (Packagist): upgrade to 4.4.37 or later

  composer require contao/core-bundle:^4.4.37

Affected products

• contao/contao (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.37
• contao/core (Packagist) ECOSYSTEM:introduced=3.0.0,fixed=3.5.39
• contao/core-bundle (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.4.37

Identifiers

• CVE-2019-10641
• GHSA-vcgg-hp4r-87gx