dbcve.org
Gatemanager 4250 FirmwareOperating system · Secomea

CVE-2022-25787

MEDIUM · 6.7 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 9.7.622134021 or later.
See remediation →
69/100
Remediation priority · Elevated
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
Information Exposure Through Query Strings in GET Request vulnerability in LMM API of Secomea GateManager allows system administrator to hijack connection. This issue affects: Secomea GateManager 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 · moderate confidence

The LMM API in Secomea GateManager versions prior to 9.7 exposes sensitive information through query strings in GET requests. This information leakage allows attackers to hijack administrative connections by intercepting the exposed query string data.

MitigationUpgrade to GateManager version 9.7 or later. Additionally, avoid transmitting sensitive data via query strings in GET requests; use POST requests or other secure methods for sensitive information.

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
Gatemanager 4250 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 4260 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 8250 FirmwareOperating system
Affected:< 9.7.622134021
Gatemanager 9250 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 Secomea GateManager firmware version
    Access the GateManager web interface or use the command line interface (CLI) to retrieve the firmware version. Typically found in the System > Status or About section of the administrative interface.
    Affected if The installed firmware version is less than 9.7.622134021 on models 4250, 4260, 8250, or 9250.
  2. Confirm GateManager model number
    Locate the model identifier in the GateManager administrative interface under System > Status or on the physical device label.
    Affected if The device model is one of: 4250, 4260, 8250, or 9250.
  3. Verify LMM API accessibility
    Check if the LMM API endpoint is exposed. Attempt to access the API path (typically /lmm/ or similar) via HTTP/HTTPS from a client machine. Inspect whether the API responds to unauthenticated or authenticated requests.
    Affected if The LMM API endpoint is accessible and responds to requests.
  4. Inspect GET request handling for sensitive data
    Use a web proxy or packet capture tool to intercept traffic between the GateManager administrative interface and client browsers. Observe whether sensitive parameters (such as session tokens, credentials, or administrative data) are transmitted via query strings in GET URLs.
    Affected if Sensitive information is visible in query strings of GET request URLs when using the LMM API.

The environment is affected if the Secomea GateManager model is 4250, 4260, 8250, or 9250 with firmware version below 9.7.622134021 and the LMM API is accessible with sensitive data exposed in GET request query strings.

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 to GateManager version 9.7 or later. Additionally, avoid transmitting sensitive data via query strings in GET requests; use POST requests or other secure methods for sensitive information.

Recommended fix Moderate confidence

GateManager 9.7.622134021 or later

  1. Identify the current GateManager firmware version on the affected device (4250, 4260, 8250, or 9250)
  2. Download the GateManager firmware version 9.7.622134021 or later from Secomea's official support portal
  3. Follow Secomea's standard firmware upgrade procedure to apply the update
  4. Verify the upgrade was successful and the version is now 9.7.622134021 or higher
  5. Confirm the vulnerability is resolved by testing the LMM API functionality

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

Fix this in Gatemanager 4250 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25787 — 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-25787 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