CVE-2017-9303: Laravel does not properly constrain the host portion of a password-reset URL

Quick answers

Is CVE-2017-9303 exploited in the wild?

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

How severe is CVE-2017-9303?

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

Which products and versions are affected?

illuminate/auth (Packagist) ECOSYSTEM:introduced=5.3.0,last_affected=5.3.31; laravel/framework (Packagist) ECOSYSTEM:introduced=5.3.0,last_affected=5.3.31; laravel/laravel (Packagist) ECOSYSTEM:introduced=5.4.0,fixed=5.4.22.

Is there a fix for CVE-2017-9303?

Yes. laravel/laravel (Packagist): upgrade to 5.4.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2017-9303?

Check whether you run illuminate/auth (Packagist), laravel/framework (Packagist) or laravel/laravel (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

• laravel/laravel (Packagist): upgrade to 5.4.22 or later

  composer require laravel/laravel:^5.4.22

Affected products

• illuminate/auth (Packagist) ECOSYSTEM:introduced=5.3.0,last_affected=5.3.31
• laravel/framework (Packagist) ECOSYSTEM:introduced=5.3.0,last_affected=5.3.31
• laravel/laravel (Packagist) ECOSYSTEM:introduced=5.4.0,fixed=5.4.22

Identifiers

• CVE-2017-9303
• GHSA-rc8x-jrrc-frfv