CriticalCVE-2007-3010

    Alcatel OmniPCX Enterprise Remote Code Execution Vulnerability (CVE-2007-3010)

    Published In CISA KEV since Sources: CVE.org

    Share

    What is affected, what to do

    An attacker can execute arbitrary commands remotely on Alcatel OmniPCX Enterprise Communication Server R7.1 and earlier via masterCGI in the Unified Maintenance Tool by injecting shell metacharacters in the user parameter during a ping action. This vulnerability allows for remote code execution (RCE) and is actively exploited in the wild, as evidenced by its listing in the CISA KEV catalog and a high EPSS of 0.9741. Affected products include version 7.1 of the Alcatel OmniPCX Enterprise Communication Server. Immediate patching is critical to mitigate this vulnerability.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Alcatel OmniPCX Enterprise lte *..7.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org

    97.4 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.90

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    228.84 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    97.4 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.90
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 7 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-77

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw is network-reachable without authentication and yields command execution with near-system privileges on a core voice-infrastructure component. Exploitation likelihood is in the very top band and working exploit code has been public for years — any UMT reachable from the internet must be treated as actively at risk. For NIS2-regulated operators, voice telephony falls under essential services; disruption or interception carries both operational and confidentiality consequences. Rank it P1 for internet-exposed instances and P2 for internally segmented ones, coupled with a lifecycle decision given that R7.1 is well past current vendor support.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Apply the vendor fix: upgrade Alcatel OmniPCX Enterprise Communication Server off R7.1 or earlier to a release flagged as patched in the Alcatel-Lucent Enterprise security advisory. Confirm the exact crossrelease number from the vendor bulletin.
      • Pull the Unified Maintenance Tool (masterCGI) off any public interface: restrict the management web service (typically TCP/80 and TCP/443 on the OmniPCX management IP) with perimeter ACLs so only a dedicated admin VLAN or jump host can reach it.
      • Run a Shodan/Censys sweep of your external IP ranges for "OmniPCX" and "masterCGI" fingerprints; treat every internet-exposed node as potentially compromised and route it into IR.
      • If patching has to wait, disable masterCGI in the UMT web server or block the URL via rewrite until the fixed release is deployed.
      • Rotate all local accounts on the Communication Server (root, mtcl, adfexc and similar) and reissue admin SSH keys, since successful exploitation yields near-root command execution.
      • Snapshot current configuration and call-routing data to offline storage before patching, so you keep a clean rollback point if compromise is later confirmed.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place telephony infrastructure in its own VLAN with explicit firewall policy; permit management only from a hardened jump host behind MFA. No direct reachability from user LANs or the internet.
      • WAF/reverse proxy in front of UMT: inspect requests to /cgi-bin/masterCGI, strip or block metacharacters (;, |, &, `, $(, newline, %0a) in the user parameter, and allowlist alphanumerics only.
      • IPS/IDS signature: Suricata/Snort rule matching HTTP requests containing masterCGI plus action=ping plus shell metacharacters in user; drop and alert.
      • Egress filtering on the telephony VLAN: constrain outbound traffic to the bare minimum (NTP, internal DNS, SIP trunk) to break reverse shells and second-stage payload downloads.
      • Host hardening: remove unused CGI scripts from UMT, run the web server under a least-privilege account, and forward local audit logs via syslog to the SIEM.
      • Lifecycle decision: OmniPCX Enterprise R7.1 is end-of-life. Document the residual risk and plan an upgrade or replacement path — this is directly relevant to NIS2 risk management obligations and ISO 27001 A.8 asset lifecycle.

    3. Runbook step 3

      Detection rules

      • Inspect UMT web access logs for GET /cgi-bin/masterCGI*action=ping*user=* with URL-encoded metacharacters (%3B, %7C, %60, %24%28). Sigma shape: category: webserver, selection.cs-uri-stem contains 'masterCGI', selection.cs-uri-query re '[;|&\x60$]'.
      • On the Linux-based Communication Server, auditd rule: execve events with parent httpd/cgi and child /bin/sh, /bin/ping, wget, curl, nc, perl escalate to high severity.
      • EDR process ancestry: web server process spawning a shell or network tool. KQL example: DeviceProcessEvents | where InitiatingProcessFileName in~ ("httpd","cgi") and FileName in~ ("sh","bash","wget","curl","nc","ping").
      • Zeek/network telemetry: correlate new outbound connections from the telephony VLAN to atypical ports (4444, 1337, 8080 to the internet) shortly after an HTTP request to masterCGI.
      • File integrity monitoring: alert immediately on changes to /etc/passwd, /etc/shadow, cron jobs, and SSH authorized_keys on the appliance.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    masterCGI in the Unified Maintenance Tool in Alcatel OmniPCX Enterprise Communication Server R7.1 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the user parameter during a ping action.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    al-enterpriseomnipcx_enterprise_communication_server
    • ≤ 7.1
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection')

      Class

      The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

      Entry at MITRE CWE-77

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • vupen.comADV-2007-3185Vulnerability database, x_refsource_VUPEN, Broken link
    • redteam-pentesting.deadvisories/rt-sa-2007-001.phpx_refsource_MISC, Broken link
    • www1.alcatel-lucent.compsirt/statements/2007002/OXEUMT.htmx_refsource_CONFIRM, Broken link
    • secunia.com26853Third-party advisory, x_refsource_SECUNIA, Broken link, Vendor advisory
    • marc.info20070917 Alcatel-Lucent OmniPCX Remote Command ExecutionMailing list, x_refsource_FULLDISC, Exploit, Mailing list
    • osvdb.org40521Vulnerability database, x_refsource_OSVDB, Broken link
    • securityfocus.com20070917 Alcatel-Lucent OmniPCX Remote Command ExecutionMailing list, x_refsource_BUGTRAQ, Broken link, Third-party advisory, Vulnerability database
    • exchange.xforce.ibmcloud.comalcatel-unified-mastercgi-command-execution(36632)Vulnerability database, x_refsource_XF, Third-party advisory, Vulnerability database
    • securityfocus.com25694Vulnerability database, x_refsource_BID, Broken link, Third-party advisory, Vulnerability database
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2007-3010government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2007-3010
    <a href="https://intel.neosec.eu/en/cve/CVE-2007-3010"><img src="https://intel.neosec.eu/badge/cve/CVE-2007-3010.svg?lang=en" alt="CVE-2007-3010 – NEOSEC Intel" height="20"></a>