Skip to main content
VulnerabilityPublished Updated

CVE-2024-41270: Gorush · Weak Cryptography

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% 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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

To mitigate CVE-2024-41270 effectively, organizations should take several specific actions beyond generic advice: 1) Immediately audit Gorush deployments to identify affected versions, focusing on v1.18.4 and any others using deprecated TLS versions. 2) Disable support for deprecated TLS protocols such as TLS 1.0 and TLS 1.1 in the Gorush server configuration and enforce TLS 1.2 or higher, ensuring strong cipher suites are used. 3) If an official patch is released, prioritize applying it promptly; monitor Gorush project repositories and security advisories for updates. 4) Implement network-level protections such as TLS interception detection, anomaly-based intrusion detection systems (IDS), and strict firewall rules to limit exposure of the Gorush server to untrusted networks. 5) Use TLS certificate pinning where possible on client applications to reduce the risk of MITM attacks. 6) Conduct regular security assessments and penetration testing focused on TLS configurations and server communications. 7) Educate development and operations teams about the risks of using deprecated cryptographic protocols and enforce secure coding and deployment practices. 8) Consider deploying Web Application Firewalls (WAFs) or reverse proxies that can enforce secure TLS configurations and provide additional inspection capabilities. These targeted steps will reduce the risk of exploitation and protect data integrity and confidentiality in Gorush environments.

Description

An issue discovered in the RunHTTPServer function in Gorush v1.18.4 allows attackers to intercept and manipulate data due to use of deprecated TLS version.

References

Community reviews

Loading reviews…