Skip to main content
Mallory
MediumVulnerability

CVE-2012-0814: Information Disclosure in OpenSSH auth_parse_options

Published Jan 27, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS3.6%90th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Openbsd
IdentifiersCVE-2012-0814CWE-200

In OpenSSH before version 5.7, the auth_parse_options function in auth-options.c leaks debug messages containing the command options from authorized_keys. This allows remote authenticated users to obtain potentially sensitive information by accessing these debug messages, even in environments where the user does not have shell or filesystem access (e.g., shared accounts used by Gitolite).

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote authenticated users can obtain sensitive information about authorized_keys command options via debug messages. This can cross privilege boundaries, as users without shell or filesystem access may still be able to read these messages, potentially exposing configuration details or command restrictions intended to be private.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to debug logs and ensure that only trusted users can access SSH debug output. Consider disabling debug logging in production environments or using log management solutions to limit exposure until the software can be upgraded.

Remediation

Patch, then assume compromise.

Upgrade OpenSSH to version 5.7 or later, where this information disclosure issue is resolved and debug messages no longer leak sensitive authorized_keys command options.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenbsdOpensshapplication
FAQ

Frequently asked questions

Is CVE-2012-0814 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2012-0814 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2012-0814?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2012-0814.
Is there a patch for CVE-2012-0814?
Upgrade OpenSSH to version 5.7 or later, where this information disclosure issue is resolved and debug messages no longer leak sensitive authorized_keys command options.
What products are affected by CVE-2012-0814?
Openbsd Openssh.
How severe is CVE-2012-0814?
CVE-2012-0814 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 3.6% (90th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.