handleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Link | Tags |
---|---|
https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf | third party advisory exploit |
https://www.usenix.org/conference/usenixsecurity20/presentation/fiterau-brostean | third party advisory |
https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0 | third party advisory patch |
https://github.com/pion/dtls/compare/v1.5.1...v1.5.2 | third party advisory patch |