Linux sshd Logs: Flag Failed Curve25519 Key Generation Indicative of libSSH CVE-2023-2283 Attempts

Alerts on sshd log entries with 'Failed to generate curve25519 keys' that may indicate CVE-2023-2283 libssh bypass attempts.

FreeReviewedSigma · Medium · v5
Product
linux
Service
sshd
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-06-09
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags SSH daemon log entries containing “Failed to generate curve25519 keys,” which can indicate a libSSH authentication-bypass attempt tied to CVE-2023-2283. Attackers may trigger this specific error condition during exploitation, and successful exploitation is not required for the event to appear. It relies on Linux sshd service telemetry that records the failure message in its logs.

Related detections9 linkedT1190 — drag to rearrange
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Ivanti Pulse Connect Secure Auth Bypass via TOTP Backup Code Path Traversal (via webserver)
Possible Citrix Bleed Session Token Leak via OpenID Configuration Endpoint (CVE-2023-4966) (via webserver)
Linux sshd Logs: Flag Failed Curve25519 Key Generation Indicative of libSSH CVE-2023-2283 Attempts
Pivot detection · T1190 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.