Skip to content
Fencer Intel
critical 9.8

CVE-2015-0936 in the critical feed json

Ceragon FibeAir IP-10 have a default SSH public key in the authorized_keys file for the mateidu user, which allows remote attackers to obta…

published 9y ago modified 4mo ago also EUVD-2015-0944

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
78.2%
EPSS 78.2% chance of exploitation in 30 days, percentile 99.5%
public exploits
2
Metasploit and Exploit-DB

Summary

Ceragon FibeAir IP-10 have a default SSH public key in the authorized_keys file for the mateidu user, which allows remote attackers to obtain SSH access by leveraging knowledge of the private key.

Is CVE-2015-0936 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/ssh/ceragon_fibeair_known_privkey)
  2. Published

Exploit prediction

78.24% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/ssh/ceragon_fibeair_known_privkey Ceragon FibeAir IP-10 SSH Private Key Exposure metasploit exploit, excellent rank, 2015-04-01
  • EDB-41679 Ceragon FibeAir IP-10 - SSH Private Key Exposure (Metasploit) remote, 2015-04-01
  • google.com https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0ahUKEwjs47SGp47UAhVF5iYKHYGLDQkQFggoMAE&url=https%3A%2F%2Fwww.rapid7.com%2Fdb%2Fmodules%2Fexploit%2Flinux%2Fssh%2Fceragon_fibeair_known_privkey&usg=AFQjCNFZiZcWj47cpqPX-AbfpsW0DL4yYw referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/131260/Ceragon-FibeAir-IP-10-SSH-Private-Key-Exposure.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.