CVE-2022-23767
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 · uneditedThis vulnerability of SecureGate is SQL-Injection using login without password. A path traversal vulnerability is also identified during file transfer. An attacker can take advantage of these vulnerabilities to perform various attacks such as obtaining privileges and executing remote code, thereby taking over the victim’s system.
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 confidenceSecureGate contains SQL injection in the login authentication mechanism allowing bypass without password, combined with a path traversal vulnerability in file transfer functionality. Chaining these flaws enables attackers to escalate privileges and achieve remote code execution.
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= 3.5>= 3.5.2, <= 3.5.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionLocate the Hanssak application installation directory and check version information in configuration files, About pages, or the application metadata. Common locations include version files, manifest files, or the main executable properties.Affected if Product is Hanssak Securegate version 3.5 OR Hanssak Weblink versions 3.5.2 through 3.5.5
-
Verify login authentication is exposedCheck if the web-based login authentication interface is accessible. Look for the login endpoint or authentication module configuration to confirm it is enabled and reachable.Affected if The login authentication mechanism is enabled and accessible to users or attackers
-
Confirm file transfer functionality is enabledInspect application configuration files or feature flags to determine if the file transfer/upload module is active. Check for file transfer-related endpoints or services.Affected if File transfer functionality is enabled in the application configuration
-
Review authentication implementationExamine authentication-related code or configuration for the presence of SQL query construction that uses unsanitized user input. Look for direct string concatenation in login queries.Affected if Authentication code uses string concatenation or unsanitized parameters in SQL queries rather than parameterized queries
-
Inspect file operation handlingReview file transfer or file operation code to check if user-supplied file paths are used without proper validation. Look for path handling in file upload/download functions.Affected if File operations accept user-controlled paths without allowlist validation or path sanitization
The environment is affected if running Hanssak Securegate 3.5 or Hanssak Weblink 3.5.2-3.5.5 with login authentication and file transfer features both enabled.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patch if available; otherwise disable vulnerable login and file transfer features, implement parameterized queries for authentication, and enforce strict input validation with allowlist-based path validation for file operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23767 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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