dbcve.org
Sitemanager 1129 FirmwareOperating system · Secomea

CVE-2022-25785

HIGH · 7.2 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 9.7.622134021 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack-based Buffer Overflow vulnerability in SiteManager allows logged-in or local user to cause arbitrary code execution. This issue affects: Secomea SiteManager all versions prior to 9.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in Secomea SiteManager versions prior to 9.7. An authenticated logged-in user or local user can exploit this buffer overflow to achieve arbitrary code execution on the affected system.

MitigationUpgrade Secomea SiteManager to version 9.7 or later to address the stack-based buffer overflow vulnerability. Since this is an authenticated attack vector, ensure strict access controls and principle of least privilege are maintained.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sitemanager 1129 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 1139 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 1149 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3329 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3339 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3349 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3529 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3539 FirmwareOperating system
Affected:< 9.7.622134021

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the SiteManager model number
    Locate the model identifier on the physical device label or in the device management interface. Common models include 1129, 1139, 1149, 3329, 3339, 3349, 3529, and 3539.
    Affected if The model is one of the listed affected models (1129, 1139, 1149, 3329, 3339, 3349, 3529, or 3539).
  2. Determine the installed firmware version
    Access the SiteManager administrative interface or use the device's firmware version check command to retrieve the currently installed firmware version number.
    Affected if The installed firmware version is earlier than 9.7.622134021.
  3. Confirm web-based management or SSH is accessible
    Verify whether the SiteManager web interface or SSH service is reachable on the network. This is required for an authenticated attacker to exploit the vulnerability.
    Affected if Remote management interfaces are exposed and accessible to untrusted networks.
  4. Review user account configuration
    Check the list of configured local users and any integrated authentication sources. Identify whether user accounts with elevated privileges exist beyond the minimum required.
    Affected if Multiple authenticated users or accounts with privileges beyond what is strictly necessary are present.

You are affected if your SiteManager model is one of the listed models and the installed firmware version is below 9.7.622134021.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.7.622134021 or later
Fixed in 9.7.622134021
Interim mitigation

Upgrade Secomea SiteManager to version 9.7 or later to address the stack-based buffer overflow vulnerability. Since this is an authenticated attack vector, ensure strict access controls and principle of least privilege are maintained.

Recommended fix High confidence

Firmware version 9.7.622134021 or later (9.7.x)

  1. 1. Log in to the SiteManager administrative interface
  2. 2. Navigate to the firmware update or system settings section
  3. 3. Download the firmware version 9.7.622134021 or later from the official Secomea support portal
  4. 4. Upload and apply the new firmware version
  5. 5. After reboot, verify the firmware version has been updated successfully
  6. 6. Confirm the SiteManager is functioning normally with the new firmware
Caveat Review release notes for any configuration or feature changes between your current version and 9.7

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sitemanager 1129 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25785 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data