CVE-2023-51767: OpenSSH through 10.0, when common types of DRAM are used, might allow row hammer attacks (for authenticatio...
OpenSSH through 10.0, when common types of DRAM are used, might allow row hammer attacks (for authentication bypass) because the integer value of authenticated in mm_answer_authpassword does not resist flips of a single bit. NOTE: this is applicable to a certain threat model of attacker-victim co-location in which the attacker has user privileges. NOTE: this is disputed by the Supplier, who states "we do not consider it to be the application's responsibility to defend against platform architectural weaknesses."
Security readout for executives and security teams
Plain-English summary
This CVE describes a theoretical OpenSSH authentication bypass under a narrow hardware threat model: an attacker already has local user access and can induce DRAM bit flips. It is serious if that co-location model exists, but the OpenSSH supplier disputes responsibility for defending against the underlying platform weakness.
Executive priority
Treat as a focused risk review, not an internet-wide emergency. Prioritize systems with untrusted local users, shared infrastructure, or sensitive administrative access. Ask infrastructure owners to confirm exposure assumptions and vendor status before disruptive remediation.
Technical view
The report concerns OpenSSH through 10.0 and a single-bit flip affecting the integer authenticated value in password authentication monitor logic. CVSS is 7.0 with local access, high complexity, and low privileges required. The issue depends on Rowhammer-prone DRAM and attacker-victim co-location.
Likely exposure
Highest concern is shared or multi-user Linux/Unix systems where untrusted users can run local workloads near SSH authentication processes on susceptible DRAM. Typical single-tenant servers with controlled local access have materially lower exposure based on the provided threat model.
Exploitation context
No KEV listing or provided source states active exploitation. The source bundle frames exploitation as Rowhammer-based, local, high-complexity, and dependent on user privileges plus hardware co-location. The supplier dispute further limits certainty about practical software remediation.
Researcher notes
Evidence centers on OpenSSH monitor/password-auth code paths and Rowhammer research. The CVE is disputed by the supplier, and the bundle does not provide a definitive upstream patch. Avoid asserting exploitability outside the stated co-location, local-privilege, susceptible-DRAM model.
Mitigation direction
Inventory systems running OpenSSH through 10.0.
Check Red Hat, Ubuntu, NetApp, and OpenSSH guidance for applicability.
Reduce untrusted local user access on potentially affected hosts.
Review multi-tenant workload placement and hardware isolation assumptions.
Apply vendor-provided packages if your vendor lists a fixed build.
Validation and detection
Confirm OpenSSH versions and vendor package status across server fleets.
Identify hosts allowing untrusted local shell or workload execution.
Assess whether deployed DRAM and tenant placement match the Rowhammer threat model.
Review authentication logs for anomalies without assuming exploit detection is reliable.
Track vendor advisories for changed status, dispute notes, or mitigations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
description · low confidence lookup
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.