CVE-2024-39223
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 · uneditedAn authentication bypass in the SSH service of gost v2.11.5 allows attackers to intercept communications via setting the HostKeyCallback function to ssh.InsecureIgnoreHostKey
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 confidenceThis is an authentication bypass vulnerability in gost v2.11.5's SSH service where the HostKeyCallback function is incorrectly set to ssh.InsecureIgnoreHostKey, disabling host key verification and allowing man-in-the-middle attacks where attackers can intercept communications.
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
- 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 gost installation and versionRun 'gost -V' or 'gost --version' to determine the installed version of gost. If gost is not in PATH, search for it using 'which gost' on Linux or 'where gost' on Windows.Affected if The version is v2.11.5 or falls within the affected version range.
-
Locate gost configuration filesSearch for gost config files in common locations such as ~/.gost/, /etc/gost/, or the working directory. Look for .yaml, .yml, .json, or config flags passed at startup. Check process arguments with 'ps aux | grep gost' to see any config file paths or flags used.Affected if A configuration file exists and contains SSH-related settings.
-
Inspect SSH HostKeyCallback configurationExamine gost configuration files or startup scripts for any SSH client or server settings. Search for the string 'HostKeyCallback' or 'InsecureIgnoreHostKey' within config files and any scripts that launch gost.Affected if The HostKeyCallback is explicitly set to ssh.InsecureIgnoreHostKey or equivalent insecure value.
-
Review SSH client connectionsIf gost is used as an SSH client to connect to remote servers, check all connection configurations. Look for CLI flags, environment variables, or config settings related to SSH host key verification.Affected if Any SSH connection from gost bypasses host key verification.
-
Check for runtime behaviorMonitor network connections and verify that gost is accepting SSH connections without validating host keys. Use 'netstat' or 'ss' to identify listening SSH ports, and review any proxy or tunnel configurations.Affected if gost is running an SSH service and connections are accepted without host key validation.
You are affected if gost v2.11.5 is installed and the SSH HostKeyCallback is configured to use ssh.InsecureIgnoreHostKey, disabling host key verification.
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 dataUpgrade gost to a patched version and ensure the SSH HostKeyCallback properly validates host keys instead of using ssh.InsecureIgnoreHostKey; review all SSH client configurations for similar insecure settings.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-39223 — 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-2024-39223 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