CVE-2022-41711: Badaso vulnerable to Remote Code Execution via malicious file upload

CVE-2022-41711 · Severity: low · CVSS 3.1 · Published 2022-10-26

Badaso vulnerable to Remote Code Execution via malicious file upload

Technologies: badaso/core (Packagist). Vendors: Packagist.

Quick answers

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

  • badaso/core (Packagist): upgrade to 2.6.1 or later
    composer require badaso/core:^2.6.1

Affected products

  • badaso/core (Packagist) ECOSYSTEM:introduced=0,fixed=2.6.1

Identifiers

  • CVE-2022-41711
  • GHSA-fwvc-9xhj-26v5

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