Our great sponsors
-
ssh-audit
SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc) (by jtesta)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
No. Mitigations are available now. Follow the recommendations from ssh-audit (master version). [0]
0. https://github.com/jtesta/ssh-audit
Unless I'm misunderstanding what this is about RFC5647 merely points out that the sequence number is included as AAD due to RFC4253 requirements. The [email protected] specification is not exactly the most rigorous thing I've ever seen (https://github.com/openssh/openssh-portable/blob/master/PROT...) but reading it, the sequence number is only included in the IV, and not as AAD, which directly runs afoul of the RFC4253 section 6.4 requirement for it to be included in the MAC.
There is now an issue ticket in ssh-mitm to discuss the similarities between ssh-mitm and terrapin attack: https://github.com/ssh-mitm/ssh-mitm/issues/165
Related posts
- SSH Agent Forwarding - What are the best practices and current security issues?
- Terrapin-Attack Style Vulnerability Likely Exploited for 2 Years
- SSH3: SSH using HTTP/3 and QUIC
- Check if a publickey is known by GitHub or Gitlab without iterating all users
- Should SSH-MITM add a Codehoster user check as a default setting?