MatrixSSL 4.0.4 through 4.5.1 has an integer overflow in matrixSslDecodeTls13. A remote attacker might be able to send a crafted TLS Message to cause a buffer overflow and achieve remote code execution. This is fixed in 4.6.0.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Link | Tags |
---|---|
https://www.telekom.com/en/company/data-privacy-and-security/news/advisories-504842 | vendor advisory |
https://github.com/matrixssl/matrixssl/security/advisories/GHSA-fmwc-gwc5-2g29 | third party advisory |
https://github.com/matrixssl/matrixssl/blob/4-6-0-open/doc/CHANGES_v4.x.md | third party advisory release notes |