Storage for Public Cloud vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited1 versions
The short answer

Storage for Public Cloud is made by Red Hat. We track 4 published vulnerabilities in it, across 1 version. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Storage for Public Cloud, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Storage for Public Cloud flaw added to the known-exploited list is CVE-2012-1823, on 25 March 2022. We keep watching the known-exploited list.

Versions

Which versions of Storage for Public Cloud do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2012-1823Exploited list, 25 Mar 2022

    PHP-CGI Query String Parameter Vulnerability

    2.0
Known exploited

Which Storage for Public Cloud vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2012-1823CriticalKnown exploited
    PHP-CGI Query String Parameter Vulnerability

    sapi/cgi/cgi_main.c in PHP, when configured as a CGI script, does not properly handle query strings, which allows remote attackers to execute arbitrary code.

    Chance of use>99%Known exploited since25 Mar 2022
Exploit likelihood

Which Storage for Public Cloud flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2012-1823CriticalKnown exploited

    sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not properly handle query strings that lack an = (equals sign) character, which allows remote...

    CVSS9.8Published11 May 2012
  2. 6.6%

    OpenStack Object Storage (swift) before 1.7.0 uses the loads function in the pickle Python module unsafely when storing and loading metadata in memcached, which allows remote attackers to execute arbitrary code via a...

    CVSS9.8Published22 Oct 2012
  3. 3.5%

    Integer signedness error in the png_inflate function in pngrutil.c in libpng before 1.4.10beta01, as used in Google Chrome before 17.0.963.83 and other products, allows remote attackers to cause a denial of service...

    CVSS8.8Published22 Mar 2012
Precursor Intelligence

Running Storage for Public Cloud? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 4 published vulnerabilities listed under the name Storage for Public Cloud, across 1 version. The most recent Storage for Public Cloud flaw added to the known-exploited list is CVE-2012-1823, on 25 March 2022.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2012-1823.

Each flaw names its own versions, usually as ranges. The newest, CVE-2012-1823, affects 2.0. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Storage for Public Cloud. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.