CVE-2024-39223: gost · Insecure Direct Object Reference
Affects gostSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubginuerzh/gostpkg:github/ginuerzh/gostOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-39223, organizations should immediately audit their SSH configurations to ensure that the HostKeyCallback function is not set to ssh.InsecureIgnoreHostKey or any equivalent insecure setting that disables host key verification. Administrators must enforce strict host key validation to prevent MITM attacks. Until an official patch or update is released by gost maintainers, consider the following specific actions: 1) Replace gost SSH service with alternative, well-maintained SSH implementations that enforce secure host key verification by default. 2) Implement network-level protections such as SSH traffic monitoring, anomaly detection, and use of VPNs or secure tunnels to reduce exposure. 3) Employ multi-factor authentication (MFA) and robust access controls to limit the impact of potential session compromise. 4) Regularly update and patch all SSH-related software once fixes become available. 5) Educate system administrators about the risks of disabling host key verification and enforce secure coding and configuration practices. 6) Conduct penetration testing and vulnerability assessments focusing on SSH services to identify and remediate insecure configurations proactively.
Description
An authentication bypass in the SSH service of gost v2.11.5 allows attackers to intercept communications via setting the HostKeyCallback function to ssh.InsecureIgnoreHostKey