Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2017-1000385: ROBOT / Bleichenbacher-style RSA padding oracle in Erlang/OTP TLS server

Published Dec 12, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.9Medium · v3
EPSS22.1%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectErlang
IdentifiersCVE-2017-1000385CWE-203 · Observable Discrepancy

CVE-2017-1000385 is a Bleichenbacher-style RSA PKCS#1 v1.5 padding oracle in the Erlang/OTP TLS server implementation. The server emits distinguishable TLS alerts for different RSA PKCS#1 v1.5 padding/format error conditions during RSA key exchange processing, creating an oracle that leaks information about the validity of the decrypted pre-master secret structure. An attacker can iteratively exploit these alert differences to perform RSA decryption and, in some scenarios, construct signatures using the server’s private key (ROBOT/Return of Bleichenbacher’s Oracle Threat class).

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.

A remote attacker can recover the TLS pre-master secret for sessions negotiated with RSA key exchange and decrypt captured TLS traffic, compromising confidentiality of encrypted communications. The oracle can also enable performing RSA operations equivalent to decryption/signing with the server private key, undermining authentication/integrity guarantees depending on how the key is used.

Mitigation

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

Disable TLS cipher suites that use RSA for key exchange (TLS_RSA_*) so that RSA PKCS#1 v1.5 decryption of the pre-master secret is not performed. Prefer (EC)DHE key exchange suites. If disabling is not possible, reduce exposure (limit who can connect, segment/ACL the service) until an upgrade is applied.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed/non-vulnerable Erlang/OTP version (e.g., for Juniper NorthStar Controller, upgrade to 3.0.1, 3.2.1, 4.0.0, or later, which include an updated Erlang). Apply vendor-provided patches/firmware updates that remove the oracle by making error handling uniform for PKCS#1 v1.5 failures.

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
Debian ProjectDebian Linuxoperating_system
ErlangErlang/OTPapplication
FAQ

Frequently asked questions

Is CVE-2017-1000385 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-1000385 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-1000385?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2017-1000385, the earliest disclosed Jun 17, 2009.
Is there a patch for CVE-2017-1000385?
Upgrade to a vendor-fixed/non-vulnerable Erlang/OTP version (e.g., for Juniper NorthStar Controller, upgrade to 3.0.1, 3.2.1, 4.0.0, or later, which include an updated Erlang). Apply vendor-provided patches/firmware updates that remove the oracle by making error handling uniform for PKCS#1 v1.5 failures.
What products are affected by CVE-2017-1000385?
Erlang/OTP and Debian Project Debian Linux.
How severe is CVE-2017-1000385?
CVE-2017-1000385 has a CVSS v3 score of 5.9 (Medium) and an EPSS score of 22.1% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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.