Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-0814

openssh: forced command option information disclosure

Overview

Published
27 Jan 2012
Modified
29 Apr 2026
Low CVE
0 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

The auth_parse_options function in auth-options.c in sshd in OpenSSH before 5.7 provides debug messages containing authorized_keys command options, which allows remote authenticated users to obtain potentially sensitive information by reading these messages, as demonstrated by the shared user account required by Gitolite. NOTE: this can cross privilege boundaries because a user account may intentionally have no shell or filesystem access, and therefore may have no supported way to read an authorized_keys file in its own home directory.

Source: OX vulnerability database

Severity

3.5 · LOW

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
Single
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:M/Au:S/C:P/I:N/A:N

Weakness: CWE-255

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

fixed 4
openssh
debian fixes for CVE-2012-0814
ReleasePackageFixed in
11 openssh 1:5.6p1-1
12 openssh 1:5.6p1-1
13 openssh 1:5.6p1-1
14 openssh 1:5.6p1-1

echo 1 release · 1 package

fixed 1
openssh
echo fixes for CVE-2012-0814
ReleasePackageFixed in
openssh 1:5.6p1-1

root.io debian 3 releases · 1 package

fixed 3
rootio-openssh
root.io debian fixes for CVE-2012-0814
ReleasePackageFixed in
11 rootio-openssh 1:5.6p1-1
12 rootio-openssh 1:5.6p1-1
13 rootio-openssh 1:5.6p1-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.