dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-3675

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Secomea GateManager (Web GUI) allows Reading Data from System Resources.This issue affects GateManager: from 11.0.623074018 before 11.0.623373051.

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

Path traversal vulnerability in Secomea GateManager web GUI allows authenticated attackers to escape the restricted directory and read sensitive system files by manipulating path references with '../' sequences. The vulnerability affects versions from 11.0.623074018 up to but not including 11.0.623373051.

MitigationUpgrade GateManager to version 11.0.623373051 or later. If immediate patching is not possible, restrict network access to the web GUI interface and monitor for anomalous file access patterns.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine GateManager version
    Access the GateManager web GUI admin interface and navigate to the system information or about page, or use the command-line interface if available to retrieve the installed software version number.
    Affected if The installed version is 11.0.623074018 or higher but lower than 11.0.623373051
  2. Confirm web GUI is enabled
    Verify that the GateManager web interface is accessible by attempting to reach the login page via HTTP/HTTPS on the configured port (typically 80 or 443, or a custom port).
    Affected if The web GUI interface is exposed and reachable on the network
  3. Check authentication configuration
    Review user accounts and authentication settings in GateManager to determine which users have access to file-related features or the web GUI.
    Affected if Any user account exists that can authenticate to the web GUI, since the vulnerability can be exploited by any authenticated attacker
  4. Inspect web server logs for path traversal attempts
    Locate and examine GateManager web server logs for requests containing '../' sequences or unusual directory traversal patterns targeting system files.
    Affected if Recent logs show attempted or successful path traversal patterns using '../' sequences

Your environment is affected if GateManager web GUI is accessible and the installed version falls between 11.0.623074018 and 11.0.623373051 (exclusive of the upper bound).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GateManager to version 11.0.623373051 or later. If immediate patching is not possible, restrict network access to the web GUI interface and monitor for anomalous file access patterns.

Recommended fix Moderate confidence

11.0.623373051 or later

  1. 1. Backup the current GateManager configuration before initiating the upgrade
  2. 2. Download the GateManager update from the official Secomea support portal or repository
  3. 3. Access the GateManager Web GUI administrative interface
  4. 4. Navigate to the System Maintenance or Software Update section
  5. 5. Upload and apply the firmware update version 11.0.623373051 or later
  6. 6. Verify the upgrade completed successfully by checking the software version in the Web GUI
  7. 7. Confirm the path traversal vulnerability is resolved by reviewing release notes or patch documentation
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading production systems

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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