dbcve.org
GatemanagerApplication · Secomea

CVE-2022-38123

HIGH · 7.2 CVSS v3.1 Published 2022-12-06
Fix available
A fix is available. Upgrade to 10.0.622395010 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
Improper Input Validation of plugin files in Administrator Interface of Secomea GateManager allows a server administrator to inject code into the GateManager interface. This issue affects: Secomea GateManager versions prior to 10.0.

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

Secomea GateManager versions prior to 10.0 contain improper input validation when processing plugin files through the Administrator Interface. This allows an authenticated server administrator to inject malicious code into the GateManager interface through plugin file uploads or processing.

MitigationUpgrade Secomea GateManager to version 10.0 or later to obtain the patched version with proper input validation for plugin files.

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
GatemanagerApplication
Affected:< 10.0.622395010

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 installed GateManager version
    Access the GateManager admin interface or check system information to locate the version number. This is typically visible on the login page, in system settings, or via CLI command 'dmcli' or similar system info command.
    Affected if The version shown is less than 10.0.622395010 (for example, 9.x.x or early 10.0 releases)
  2. Verify Administrator Interface access
    Confirm that the web-based Administrator Interface is enabled and accessible. Check via the management console or by attempting to reach the /admin or similar endpoint.
    Affected if The Administrator Interface is accessible and functional on the target system
  3. Confirm plugin upload capability exists
    Log into the Administrator Interface and navigate to the Plugins or Extensions section. Check if the functionality to upload or install plugin files is present.
    Affected if Plugin file upload or processing functionality is available in the admin interface
  4. Review plugin processing configuration
    Check the GateManager configuration files or settings for any plugin-related processing modules. Look for entries related to plugin handling in the system configuration.
    Affected if Plugin processing features are enabled or configured

The system is affected if the installed Secomea GateManager version is below 10.0.622395010 AND the Administrator Interface with plugin upload/processing capability is accessible.

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 10.0.622395010 or later
Fixed in 10.0.622395010
Interim mitigation

Upgrade Secomea GateManager to version 10.0 or later to obtain the patched version with proper input validation for plugin files.

Recommended fix Moderate confidence

Secomea GateManager version 10.0.622395010 or later

  1. 1. Identify the current GateManager version installed in your environment
  2. 2. If version is below 10.0.622395010, plan for an upgrade to version 10.0.622395010 or later
  3. 3. Backup the current GateManager configuration before performing the upgrade
  4. 4. Download the updated GateManager version from Secomea's official source (www.secomea.com)
  5. 5. Follow Secomea's standard upgrade procedure for GateManager
  6. 6. After upgrade, verify the version number reflects 10.0.622395010 or newer
  7. 7. Test the Administrator Interface plugin functionality to confirm the fix works
Caveat Review Secomea release notes for any compatibility changes or migration requirements between your current version and 10.0

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

Fix this in Gatemanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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