Vulnerability in wolfSSL Inc. wolfSSH

[ Why it matters ]Priority signals

• Critical severity: CVSS 9.1

[ Description ]Official description

In wolfSSH through 1.5.0 built with --enable-fwd, DoChannelOpen() in src/internal.c gates only direct-tcpip channel opens with the forwarding policy callback. forwarded-tcpip opens are admitted without an authorization check and are not capped in number, allowing a malicious SSH peer to make an endpoint allocate unbounded per-channel buffers for forwarding channels the application never authorized. A client also does not check a forwarded-tcpip open against the forwards it registered with a tcpip-forward request, as RFC 4254 section 7.2 requires, so a malicious server can open forwarding channels for addresses and ports the client never asked it to forward.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ References ]References

• github.com/wolfSSL/wolfssh/commit/616eb681e70759c30c3ba158f2b18d7bd954def8Patch
• github.com/wolfSSL/wolfssh/commit/79a7f299337a28aa561409688a268d0efe6e295cPatch
• github.com/wolfSSL/wolfssh/commit/e396a0a4b6b367f10270287446a4be0071742b5cPatch