Pureapplication System vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited34 versions
The short answer

Pureapplication System is made by IBM. We track 10 published vulnerabilities in it, across 34 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 28 January 2022. If you run Pureapplication System, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Pureapplication System flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022. We keep watching the known-exploited list.

Versions

Which versions of Pureapplication System do the exploited flaws hit?

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

  • CVE-2014-6271Exploited list, 28 Jan 2022

    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    1.0.0.0 to 1.0.0.41.1.0.0 to 1.1.0.42.0.0.0
  • CVE-2014-7169Exploited list, 28 Jan 2022

    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    1.0.0.0 to 1.0.0.41.1.0.0 to 1.1.0.42.0.0.0
Known exploited

Which Pureapplication System vulnerabilities are being exploited?

2 flaws are 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-2014-6271CriticalKnown exploited
    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.

    Chance of use>99%Known exploited since28 Jan 2022
  2. 9.8
    CVE-2014-7169CriticalKnown exploited
    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.

    Chance of use>99%Known exploited since28 Jan 2022
Exploit likelihood

Which Pureapplication System 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-2014-6271CriticalKnown exploited

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by...

    CVSS9.8Published24 Sep 2014
  2. >99%
    CVE-2014-7169CriticalKnown exploited

    GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown...

    CVSS9.8Published25 Sep 2014
  3. 95%

    Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1)...

    CVSS10.0Published28 Jan 2015
  4. 3.7%

    Multiple directory traversal vulnerabilities in the file-upload feature in IBM PureApplication System 1.0 before 1.0.0.4 iFix 10, 1.1 before 1.1.0.5, and 2.0 before 2.0.0.1 and Workload Deployer 3.1.0.7 before IF5...

    CVSS9.0Published10 Jan 2015
  5. 1.5%

    IBM PureApplication System 2.2.3.0 through 2.2.5.3 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts.

    CVSS7.5Published26 Jun 2019
  6. 1.3%

    IBM PureApplication System 2.2.3.0 through 2.2.5.3 is vulnerable to SQL injection.

    CVSS8.8Published26 Jun 2019
  7. 0.9%

    IBM PureApplication System 2.2.3.0 through 2.2.5.3 weakness in the implementation of locking feature in pattern editor.

    CVSS4.3Published26 Jun 2019
  8. 0.6%

    IBM PureApplication System 1.0 before 1.0.0.4 cfix8 and 1.1 before 1.1.0.4 IF1 allows remote authenticated users to bypass intended access restrictions by establishing an SSH session from a deployed virtual machine.

    CVSS6.6Published14 Jun 2014
  9. 0.4%

    IBM PureApplication System 2.2.3.0 through 2.2.5.3 could allow an authenticated user with local access to bypass authentication and obtain administrative access.

    CVSS7.8Published26 Jun 2019
  10. 0.4%

    IBM PureApplication System 2.2.3.0 through 2.2.5.3 stores potentially sensitive information in log files that could be read by a local user.

    CVSS4.4Published26 Jun 2019
EdgeProtect

Running Pureapplication System? 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 10 published vulnerabilities listed under the name Pureapplication System, across 34 versions. The most recent Pureapplication System flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2014-6271 and CVE-2014-7169.

Each flaw names its own versions, usually as ranges. The newest, CVE-2014-6271, affects 1.0.0.0 to 1.0.0.4, 1.1.0.0 to 1.1.0.4, 2.0.0.0. The versions for every exploited flaw are listed on this page.

Create a EdgeProtect account and track Pureapplication System. 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.