☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2021-32003

CVE-2021-32003 — Configuration service port remains open 10 minutes after reboot even when already provisioned
📅 PUBLISHED: 2021-08-05 00:00 UTC 🔄 UPDATED: 2026-08-12 17:45 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.23%
👁️
0.23% probability
5.7× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Country: Denmark License: Commercial
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
8.0
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2021-32003 is a high-severity vulnerability (CVSS 8.0) affecting the SiteManager provisioning service of Secomea SiteManager hardware devices running versions prior to 9.5. The vulnerability is classified as an Unprotected Transport of Credentials, enabling a local attacker to capture sensitive credentials if the provisioning service remains active after the device has been configured. Critically, the configuration service port remains open for 10 minutes after a reboot even when the device is already provisioned, extending the attack window. Organizations using Secomea SiteManager edge gateways for remote industrial and OT access should treat this as an elevated risk given the current lack of an available patch from tracked sources.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

The vulnerability stems from a failure in the SiteManager provisioning service to properly secure credential transport after the initial provisioning phase has completed. Per the CNA title, the configuration service port remains open for a 10-minute window following a system reboot, even when the device has already been provisioned and is in a production state. This design flaw means that the provisioning service — which is intended to handle initial setup and credential exchange — becomes accessible during every reboot cycle, not just at first-time deployment.

From a technical standpoint, the vulnerability class is Unprotected Transport of Credentials (mapping to CWE-523 or CWE-319 class behavior, though no explicit CWE ID was provided). The attack mechanism involves a local actor intercepting or capturing credentials as they are transmitted over the provisioning channel. Because the service does not employ adequate transport-layer protection (e.g., encryption or mutually authenticated channels) for credential exchange post-provisioning, any local user with access to the device's network interface during the 10-minute window can passively capture plaintext or weakly-protected credentials.

The attack surface is local — the attacker requires physical or logical local access to the SiteManager device's network segment. The NVD description explicitly states "local attacker," indicating that remote network-based exploitation without prior access is not the primary vector. However, in OT/ICS environments, the SiteManager is often deployed at remote sites, and a compromised local network (e.g., via a rogue device in the plant floor LAN) could provide the necessary foothold.

The affected hardware revision is explicitly noted as "on Hardware," suggesting the flaw is embedded in the device firmware's boot and provisioning sequence rather than purely in software logic. All versions prior to 9.5 are vulnerable.

Exploitation Scenarios

No public PoC or exploit code is currently known; the attack chain below is inferred from the vulnerability class and NVD description.

Step 1 — Reconnaissance / Target Identification: An attacker with local network access to a Secomea SiteManager device identifies the target. The attacker scans for open configuration/provisioning service ports on the device. Following any reboot of the device (whether scheduled maintenance, power cycle, or induced by the attacker if they have physical access), the provisioning service port remains open for 10 minutes — a predictable and recurring window. Shodan-style network scanning may reveal device presence, though the local nature of the attack limits remote discovery to adjacent network segments.

Step 2 — Triggering the Flaw: The attacker waits for (or induces) a device reboot. Upon reboot, the provisioning service becomes active and remains listening for 10 minutes regardless of whether the device was previously provisioned. The attacker passively monitors traffic on the provisioning service port during this window.

Step 3 — Payload/Execution Method (Vulnerability-Class Level): Because the transport of credentials is unprotected, the attacker captures credentials as they are transmitted. Two sub-scenarios exist:

  • Passive sniffing: If the device re-attempts communication with a management server or if a local operator initiates provisioning interaction during the window, credentials (e.g., device passwords, site keys, or management credentials) transit the unprotected channel and are captured.
  • Active interception: The attacker may impersonate the legitimate provisioning endpoint if the service does not verify server identity, causing the device to disclose credentials directly to the attacker.

Step 4 — Post-Exploitation Impact: Captured credentials grant the attacker authenticated access to the SiteManager device. Depending on the privilege level of the captured credentials, the attacker could:

  • Modify device configuration to redirect remote access tunnels.
  • Establish persistent unauthorized access to the OT network the SiteManager bridges.
  • Pivot to connected industrial controllers and other OT assets.

The attack is exacerbated by the predictable 10-minute window — a reboot-triggered opportunity that repeats on every power cycle, allowing repeated capture attempts.

Impact Assessment

CVSS Score: 8.0 (High). The CVSS vector string is not provided in the available data, but the score indicates significant confidentiality impact with limited availability/integrity implications.

Business Impact:

  • Confidentiality breach: Credential theft compromises the authentication fabric of the OT remote access solution.
  • Unauthorized OT access: SiteManager devices are purpose-built for remote access to industrial networks; credential compromise can lead to unauthorized control of connected OT assets.
  • Compliance failure: Organizations in regulated sectors (energy, manufacturing, utilities) may face audit findings and regulatory penalties for inadequate control of privileged credentials.

Affected Systems:

  • Secomea SiteManager hardware devices running all versions prior to 9.5. The vulnerability is hardware-specific, meaning firmware updates, not just software patches, are required.

Blast Radius: The risk is concentrated in ICS/OT environments where SiteManager acts as a remote access gateway. A single compromised device can expose multiple downstream industrial assets. The local attack requirement reduces initial exploitability, but the recurring 10-minute window increases the likelihood of eventual compromise in environments with untrusted local access or weak network segmentation.

Exploitability Factors:

  • EPSS score: 0.00228 (13.7th percentile of exploited CVEs) — currently low real-world exploitation.
  • CISA KEV: Not listed — no confirmed in-the-wild exploitation by US government standards.
  • PoC/Exploit: Unknown/None — mitigates near-term risk but does not preclude private exploit development.

Detection Guidance

The following detection rules are generated based on the vulnerability class (credential capture over an unprotected provisioning service) and the known 10-minute service window. Rules are generic and should be tuned to the Secomea SiteManager environment.

Sigma Rule

title: Secomea SiteManager Provisioning Service Credential Exposure
id: 4a8f8c0e-5a2b-4d7e-9c1a-3b2f4d6e8a10
status: experimental
description: Detects reboots or provisioning service activity on Secomea SiteManager devices that may indicate credential capture attempts
logsource:
  category: process_creation
  product: windows
  definition: Requires process telemetry from hosts managing Secomea SiteManager devices
detection:
  selection_reboot:
    EventID:
      - 1074  # System reboot initiated
      - 6005  # Event log service started (post-boot)
      - 6006  # Event log service stopped (pre-shutdown)
  selection_site:  # Adjust to match SiteManager management process paths if known
    Image|contains:
      - 'secomea'
      - 'sitemanager'
  condition: selection_reboot or selection_site
  timeframe: 10m
fields:
  - Computer
  - Image
  - User
falsepositives:
  - Legitimate scheduled maintenance reboots
  - Normal SiteManager management console activity
level: medium

YARA Rule

rule Secomea_SiteManager_Credential_Capture
{
    meta:
        author = "Valters IT Security Research"
        description = "Detects strings commonly associated with Secomea SiteManager provisioning and unprotected credential transport"
        cve = "CVE-2021-32003"
        date = "2024"
    strings:
        $a1 = "SiteManager" ascii nocase
        $a2 = "provisioning" ascii nocase
        $a3 = "Sitemanager" ascii nocase
        $b1 = "credential" ascii nocase
        $b2 = "password" ascii nocase
        $b3 = "secret" ascii nocase
    condition:
        (3 of ($a*) and 1 of ($b*)) or
        (all of ($a*) and filesize < 2MB)
}

Suricata IDS Rule

alert tcp any any -> any any (msg:"CVE-2021-32003 Secomea SiteManager Provisioning Service Credential Exposure"; flow:established; content:"SiteManager"; nocase; content:"provisioning"; nocase; content:"credential"; nocase; classtype:attempted-admin; sid:20210003; rev:1; metadata:created_at 2024_01_01, updated_at 2024_01_01, cve CVE-2021-32003)

Elastic Detection

// Detect processes referencing Secomea SiteManager provisioning
process where wildcard(process.executable, "*secomea*") or process.args in ("SiteManager", "provisioning")
// Extend detection window to 10 minutes around reboot events
| with span start where process.name == "services.exe"
  or event.code in ("6005", "6006", "1074")

Splunk SPL Query

index=windows OR index=endpoint
(EventCode=1074 OR EventCode=6005 OR EventCode=6006)
OR
(process_path="*secomea*" OR process_name="*SiteManager*")
| eval alarm="CVE-2021-32003_Credential_Exposure"
| table _time, host, user, process_name, process_path
| sort - _time
| stats count by host, alarm

Wazuh OSSEC Rule

<group name="secomea,">
  <rule id="215150" level="8">
    <if_sid>0000</if_sid>
    <match>secomea|SiteManager|sitemanager</match>
    <description>CVE-2021-32003: Secomea SiteManager provisioning service activity detected</description>
    <group>vulnerability,credential_access,</group>
  </rule>
  <rule id="215151" level="5">
    <if_sid>0000</if_sid>
    <match>1074|6005|6006</match>
    <description>System reboot event on host with potential Secomea SiteManager exposure</description>
    <group>vulnerability,reboot,</group>
  </rule>
</group>

Mitigation & Patch Guidance

Patch Status: 0/4 confidence — no patch evidence from any tracked source. No vendor fix or workaround is available per the supplied data. The vendor (Secomea) has not published a patched version beyond 9.5 (which is the fixed version per the NVD description, though no explicit patch advisory has been confirmed).

Immediate Mitigations (apply now):

  1. Network segmentation: Isolate Secomea SiteManager devices on a dedicated VLAN with strict firewall rules limiting access to the provisioning service port except during authorized provisioning from trusted management hosts.
  2. Disable provisioning service post-provisioning: If the device firmware allows it, manually disable the provisioning service after initial setup and after every reboot if permitted by operational requirements.
  3. Limit local access: Restrict physical and logical access to the SiteManager device network segment. Use 802.1X port authentication on OT LAN segments to prevent rogue device insertion.
  4. Monitor reboots: Implement the detection rules above to alert on every reboot event of a SiteManager device, since each reboot opens a 10-minute credential exposure window.
  5. Change credentials on every reboot: If feasible, rotate all SiteManager and downstream device credentials after each reboot until a patch is available.

Patch/Upgrade Steps:

  1. Monitor Secomea advisory channels for an official patch or upgraded firmware addressing CVE-2021-32003.
  2. Upgrade all SiteManager devices to version 9.5 or later once the vendor confirms the fix addresses the credential exposure vector. The NVD description explicitly states versions "prior to 9.5" are affected — plan upgrades to 9.5 or the latest available version.
  3. Test the upgraded firmware in a staging environment that mirrors production OT conditions before fleet-wide deployment.

Long-Term Hardening:

  1. Establish a firmware update cadence for all OT edge devices, matching the rigor applied to IT infrastructure patching.
  2. Deploy a centralized credential management solution (e.g., privileged access management for OT) to reduce reliance on device-stored credentials.
  3. Conduct regular OT network security assessments, specifically testing the behavior of devices during reboot cycles.
  4. Require the vendor to provide a hardened configuration baseline and guidance for disabling non-essential services.

References

  1. NVD Entry: https://nvd.nist.gov/vuln/detail/CVE-2021-32003
  2. Secomea Product Page: https://www.secomea.com/ (for vendor advisory monitoring; no specific advisory URL available in the provided data)
  3. CISA Known Exploited Vulnerabilities Catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (confirming CVE-2021-32003 is NOT listed — no in-the-wild exploitation recorded)
  4. FIRST EPSS: https://www.first.org/epss/ (EPSS score 0.00228, 13.7% percentile)

Threat Actor Campaigns / Exploit-in-the-Wild Evidence: None identified in the supplied data. No public proof-of-concept, exploit code, or confirmed in-the-wild campaigns were reported. The CISA KEV catalog does not list this vulnerability, and the EPSS percentile (13.7%) indicates low observed exploitation activity. However, the absence of public exploit data does not rule out targeted use by actors with local OT network access, particularly in industrial sectors where SiteManager devices are prevalent.

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2021-32003/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.