CVE-2022-3607: PYSEC-2022-42975 - Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository octoprint/octoprint prior to 1.

CVE-2022-3607 · Severity: low · CVSS 3 · Published 2022-10-19

Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository octoprint/octoprint prior to 1.8.3.

Technologies: OctoPrint (PyPI). Vendors: PyPI.

Quick answers

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

  • OctoPrint (PyPI): upgrade to 1.8.3 or later
    pip install "OctoPrint>=1.8.3"

Affected products

  • OctoPrint (PyPI) ECOSYSTEM:introduced=0,fixed=1.8.3, GIT:introduced=0,fixed=3cca3a43f3d085e9bbe5a5840c8255bb1b5d052e|ECOSYSTEM:introduced=0,fixed=1.8.3

Identifiers

  • CVE-2022-3607
  • GHSA-rj5f-vm79-5j84
  • PYSEC-2022-42975

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