Commerce Server vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited4 versions
The short answer

Commerce Server is made by Microsoft. We track 9 published vulnerabilities listed under that exact name, across 4 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 3 March 2022. Microsoft lists newer releases under their own names, such as Commerce Server 2009, so check those pages too.

Check your version

The most recent Commerce Server flaw added to the known-exploited list is CVE-2012-1856, on 3 March 2022. We keep watching the known-exploited list.

Other names

Is Commerce Server listed under other names? Yes.

Microsoft also lists Commerce Server under more specific names, such as Commerce Server 2009. 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 Commerce Server 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-1856Exploited list, 3 Mar 2022

    Microsoft Office MSCOMCTL.OCX Remote Code Execution Vulnerability

    2002-sp42007-sp220092009-r2
  • CVE-2012-0158Exploited list, 3 Nov 2021

    Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability

    2002-sp42007-sp2
Known exploited

Which Commerce Server 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. 8.8
    CVE-2012-1856HighKnown exploited
    Microsoft Office MSCOMCTL.OCX Remote Code Execution Vulnerability

    The TabStrip ActiveX control in the Common Controls in MSCOMCTL.OCX in Microsoft Office allows remote attackers to execute arbitrary code via a crafted (1) document or (2) web page that triggers system-state corruption.

    Chance of use72%Known exploited since3 Mar 2022
  2. 8.8
    CVE-2012-0158HighKnown exploited
    Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability

    Microsoft MSCOMCTL.OCX contains an unspecified vulnerability that allows for remote code execution, allowing an attacker to take complete control of an affected system under the context of the current user.

    Chance of use>99%Known exploited since3 Nov 2021
Exploit likelihood

Which Commerce Server 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. 30%

    The sample files in the authfiles directory in Microsoft Commerce Server 2002 before SP2 allow remote attackers to bypass authentication by logging in to authfiles/login.asp with a valid username and any password,...

    CVSS7.5Published19 Mar 2006
  2. 29%

    Unspecified vulnerability in certain COM objects in Microsoft Office Web Components 2000 allows user-assisted remote attackers to execute arbitrary code via vectors related to DataSource that trigger memory...

    CVSS9.3Published11 Mar 2008
  3. 20%

    Buffer overflow in AuthFilter ISAPI filter on Microsoft Commerce Server 2000 and 2002 allows remote attackers to execute arbitrary code via long authentication data, aka "New Variant of the ISAPI Filter Buffer Overrun".

    CVSS7.5Published3 Jul 2002
  4. 19%

    The Office Web Components (OWC) package installer for Microsoft Commerce Server 2000 allows remote attackers to execute commands by passing the commands as input to the OWC package installer, aka "OWC Package Command...

    CVSS7.5Published3 Jul 2002
  5. 17%

    Buffer overflow in the Office Web Components (OWC) package installer used by Microsoft Commerce Server 2000 allows remote attackers to cause the process to fail or run arbitrary code in the LocalSystem security...

    CVSS5.0Published3 Jul 2002
  6. 13%

    Buffer overflow in AuthFilter ISAPI filter on Microsoft Commerce Server 2000 allows remote attackers to execute arbitrary code via long authentication data.

    CVSS7.5Published8 Mar 2002
  7. 12%

    Buffer overflow in the Profile Service of Microsoft Commerce Server 2000 allows remote attackers to cause the server to fail or run arbitrary code in the LocalSystem security context via an input field using an...

    CVSS5.0Published3 Jul 2002
Precursor Intelligence

Running Commerce Server? 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 9 published vulnerabilities listed under the name Commerce Server, across 4 versions. The most recent Commerce Server flaw added to the known-exploited list is CVE-2012-1856, on 3 March 2022.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2012-1856 and CVE-2012-0158.

Microsoft also lists Commerce Server under more specific names, such as Commerce Server 2009. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Each flaw names its own versions, usually as ranges. The newest, CVE-2012-1856, affects 2002-sp4, 2007-sp2, 2009, 2009-r2. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Commerce Server. 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.