CVE-2009-3628: TYPO3 Backend Discloses Encryption Key

CVE-2009-3628 · Severity: info · Published 2022-05-02

TYPO3 Backend Discloses Encryption Key

Technologies: typo3/cms-backend (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2009-3628 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2009-3628 being exploited in the wild.
How severe is CVE-2009-3628?
Informational severity, published 2 May 2022.
Which products and versions are affected?
typo3/cms-backend (Packagist) ECOSYSTEM:introduced=0,last_affected=4.0.13.
Is there a fix for CVE-2009-3628?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2009-3628?
Check whether you run typo3/cms-backend (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.

Affected products

  • typo3/cms-backend (Packagist) ECOSYSTEM:introduced=0,last_affected=4.0.13

Identifiers

  • CVE-2009-3628
  • GHSA-2wgg-c8xc-7gg3

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