CVE-2017-12867: SimpleSAMLphp Invalid token creation and validation

CVE-2017-12867 · Severity: low · CVSS 3 · Published 2022-05-13

SimpleSAMLphp Invalid token creation and validation

Technologies: simplesamlphp/simplesamlphp (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2017-12867 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-12867 being exploited in the wild.
How severe is CVE-2017-12867?
Low severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?
simplesamlphp/simplesamlphp (Packagist) ECOSYSTEM:introduced=1.14.0,fixed=1.14.15.
Is there a fix for CVE-2017-12867?
Yes. simplesamlphp/simplesamlphp (Packagist): upgrade to 1.14.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-12867?
Check whether you run simplesamlphp/simplesamlphp (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

  • simplesamlphp/simplesamlphp (Packagist): upgrade to 1.14.15 or later
    composer require simplesamlphp/simplesamlphp:^1.14.15

Affected products

  • simplesamlphp/simplesamlphp (Packagist) ECOSYSTEM:introduced=1.14.0,fixed=1.14.15

Identifiers

  • CVE-2017-12867
  • GHSA-597c-mh7m-48v7

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