Your message dated Tue, 23 Sep 2025 07:06:12 +0000
with message-id <anjg5j7qk7eim...@inutil.org>
and subject line Closing
has caused the Debian Bug report #1059393,
regarding openssh: CVE-2023-51767
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1059393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:9.6p1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org>

Hi Colin,

The following vulnerability was published for openssh. This is for now
just to track the issue as pointed out by a current paper. Apparently
openssh and sudo got CVEs assigned for their respective issues.

CVE-2023-51767[0]:
| OpenSSH through 9.6, 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-51767
    https://www.cve.org/CVERecord?id=CVE-2023-51767
[1] https://arxiv.org/abs/2309.02545

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

--- End Message ---
--- Begin Message ---
As per https://www.openwall.com/lists/oss-security/2025/09/22/1

--- End Message ---

Reply via email to