Application Processing Engine vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Application Processing Engine is made by Siemens. We track 2 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 4 May 2022. Siemens lists newer releases under their own names, such as Application Processing Engine Firmware, so check those pages too.

Check your version

The most recent Application Processing Engine flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022. We keep watching the known-exploited list.

Other names

Is Application Processing Engine listed under other names? Yes.

Siemens also lists Application Processing Engine under more specific names, such as Application Processing Engine Firmware. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Versions

Which versions of Application Processing Engine do the exploited flaws hit?

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

Known exploited

Which Application Processing Engine 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. 7.5
    CVE-2014-0160HighKnown exploited
    OpenSSL Information Disclosure Vulnerability

    The TLS and DTLS implementations in OpenSSL do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information.

    Chance of use>99%Known exploited since4 May 2022
Exploit likelihood

Which Application Processing Engine 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-0160HighKnown exploited

    The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via...

    CVSS7.5Published7 Apr 2014
  2. 95%

    OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master...

    CVSS7.4Published5 Jun 2014
EdgeProtect

Running Application Processing Engine? 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 2 published vulnerabilities listed under the name Application Processing Engine, across 0 versions. The most recent Application Processing Engine flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022.

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

Siemens also lists Application Processing Engine under more specific names, such as Application Processing Engine Firmware. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a EdgeProtect account and track Application Processing Engine. 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.