{"id":"CVE-2017-7746","aliases":["DEBIAN-CVE-2017-7746","DLA-1634-1","EUVD-2017-16721","GHSA-vxr4-jxwh-jjcg","SUSE-SU-2017:1174-1","SUSE-SU-2017:1442-1","UBUNTU-CVE-2017-7746","openSUSE-SU-2024:11513-1"],"status":"published","title":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite...","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","severity":{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.0247,"percentile":0.84615,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-835"],"published":"2017-04-12T23:00:00Z","modified":"2026-10-24T10:30:25Z","fixes":[{"ecosystem":"Debian:12","package":"wireshark","fixed_in":["2.2.6+g32dac6a-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"wireshark","fixed_in":["2.2.6+g32dac6a-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"wireshark","fixed_in":["2.2.6+g32dac6a-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"wireshark","fixed_in":["2.6.3-1~ubuntu14.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"wireshark","fixed_in":["2.6.3-1~ubuntu16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"wireshark","fixed_in":["2.6.3-1~ubuntu18.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6+g32dac6a-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6+g32dac6a-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6+g32dac6a-1"}]}]},{"source":"osv","ecosystem":"Debian:8","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.1+g01b65bf-4+deb8u16"}]}],"versions":["1.12.1+g01b65bf-4","1.12.1+g01b65bf-4+deb8u1","1.12.1+g01b65bf-4+deb8u10","1.12.1+g01b65bf-4+deb8u11","1.12.1+g01b65bf-4+deb8u12","1.12.1+g01b65bf-4+deb8u13","1.12.1+g01b65bf-4+deb8u14","1.12.1+g01b65bf-4+deb8u15","1.12.1+g01b65bf-4+deb8u2","1.12.1+g01b65bf-4+deb8u3","1.12.1+g01b65bf-4+deb8u4","1.12.1+g01b65bf-4+deb8u5","1.12.1+g01b65bf-4+deb8u6","1.12.1+g01b65bf-4+deb8u6~deb7u1","1.12.1+g01b65bf-4+deb8u6~deb7u10","1.12.1+g01b65bf-4+deb8u6~deb7u11","1.12.1+g01b65bf-4+deb8u6~deb7u2","1.12.1+g01b65bf-4+deb8u6~deb7u3","1.12.1+g01b65bf-4+deb8u6~deb7u4","1.12.1+g01b65bf-4+deb8u6~deb7u5","1.12.1+g01b65bf-4+deb8u6~deb7u6","1.12.1+g01b65bf-4+deb8u6~deb7u7","1.12.1+g01b65bf-4+deb8u6~deb7u8","1.12.1+g01b65bf-4+deb8u6~deb7u9","1.12.1+g01b65bf-4+deb8u7","1.12.1+g01b65bf-4+deb8u8","1.12.1+g01b65bf-4+deb8u9"],"bundled":41},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.12-36.1"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.12-36.1"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.12-36.1"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP1","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP1","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.6-44.3"}]}],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.3-1~ubuntu14.04.1"}]}],"versions":["1.10.2-1","1.10.3-1","1.10.5-1ubuntu1","1.10.5-2","1.10.6-1","1.12.1+g01b65bf-4+deb8u11ubuntu0.14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.3-1~ubuntu16.04.1"}]}],"versions":["1.12.7+g7fc8978-1","1.12.8+g5b6e543-2","2.0.1+g59ea380-3build1","2.0.2+ga16e22e-1","2.2.6+g32dac6a-2ubuntu0.16.04"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.3-1~ubuntu18.04.1"}]}],"versions":["2.4.2-1","2.4.3-1","2.4.4-1","2.4.5-1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"wireshark","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.8-1.2"}]}],"bundled":163}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"wireshark","product":"wireshark"}],"references":[{"url":"https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=58e69cc769dea24b721abd8a29f9eedc11024b7e","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13576","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Vendor Advisory","fix","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory"]},{"url":"http://www.securityfocus.com/bid/97635","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://www.wireshark.org/security/wnpa-sec-2017-19.html","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-7746"},{"url":"https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=58e69cc769dea24b721abd8a29f9eedc11024b7e","tags":["report"]},{"url":"https://github.com/advisories/GHSA-vxr4-jxwh-jjcg"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-7746","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20171174-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1002981","tags":["report"]},{"url":"https://bugzilla.suse.com/1010735","tags":["report"]},{"url":"https://bugzilla.suse.com/1010740","tags":["report"]},{"url":"https://bugzilla.suse.com/1010752","tags":["report"]},{"url":"https://bugzilla.suse.com/1010754","tags":["report"]},{"url":"https://bugzilla.suse.com/1010911","tags":["report"]},{"url":"https://bugzilla.suse.com/1021739","tags":["report"]},{"url":"https://bugzilla.suse.com/1025913","tags":["report"]},{"url":"https://bugzilla.suse.com/1027998","tags":["report"]},{"url":"https://bugzilla.suse.com/1033936","tags":["report"]},{"url":"https://bugzilla.suse.com/1033937","tags":["report"]},{"url":"https://bugzilla.suse.com/1033938","tags":["report"]},{"url":"https://bugzilla.suse.com/1033939","tags":["report"]},{"url":"https://bugzilla.suse.com/1033940","tags":["report"]},{"url":"https://bugzilla.suse.com/1033941","tags":["report"]},{"url":"https://bugzilla.suse.com/1033942","tags":["report"]},{"url":"https://bugzilla.suse.com/1033943","tags":["report"]},{"url":"https://bugzilla.suse.com/1033944","tags":["report"]},{"url":"https://bugzilla.suse.com/1033945","tags":["report"]},{"url":"https://bugzilla.suse.com/998761","tags":["report"]},{"url":"https://bugzilla.suse.com/998762","tags":["report"]},{"url":"https://bugzilla.suse.com/998763","tags":["report"]},{"url":"https://bugzilla.suse.com/998800","tags":["report"]},{"url":"https://bugzilla.suse.com/998963","tags":["report"]},{"url":"https://bugzilla.suse.com/998964","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7748","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20171442-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1026507","tags":["report"]},{"url":"https://bugzilla.suse.com/1027692","tags":["report"]},{"url":"https://bugzilla.suse.com/990856","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6354","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2017-7746","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-7746","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2006-1932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-4574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-4805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-5468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-5469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-5740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-0456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-0457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-0458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-0459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19626","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-9273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-13619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-17498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-28030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-7044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-9428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-9429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-9430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-9431","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22235","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-7746","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:00:00Z","modified":"2024-08-05T16:12:28.347Z","updated_at":"2026-11-02T14:33:20.843976Z"}],"euvd":[{"id":"EUVD-2017-16721","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:00:00Z","modified":"2024-08-05T16:12:28Z","updated_at":"2026-11-03T02:39:07.559484Z"}],"ghsa":[{"id":"GHSA-vxr4-jxwh-jjcg","title":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite...","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2022-05-13T01:47:07Z","modified":"2025-04-20T03:37:05Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-835"],"updated_at":"2026-11-02T15:01:44.663713Z"}],"nvd":[{"id":"CVE-2017-7746","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:59:00.417Z","modified":"2026-06-17T01:25:06.493Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-835"],"updated_at":"2026-11-02T14:03:46.08744Z"}],"osv":[{"id":"CVE-2017-7746","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:59:00.417Z","modified":"2026-10-24T10:30:25.51745463Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:06.412595Z"},{"id":"DEBIAN-CVE-2017-7746","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:59:00.417Z","modified":"2026-09-01T20:03:50.430119188Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:29.698576Z"},{"id":"UBUNTU-CVE-2017-7746","description":"In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.","status":"published","published":"2017-04-12T23:59:00Z","modified":"2026-04-22T11:32:43.894303Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:15.773974Z"},{"id":"DLA-1634-1","title":"wireshark - security update","status":"published","published":"2019-01-15T00:00:00Z","modified":"2026-03-09T01:21:39.898821Z","updated_at":"2026-11-02T15:46:09.777694Z"},{"id":"openSUSE-SU-2024:11513-1","title":"libwireshark14-3.4.8-1.2 on GA media","description":"These are all security issues fixed in the libwireshark14-3.4.8-1.2 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:58:40.825311Z","updated_at":"2026-11-02T16:58:35.195147Z"},{"id":"SUSE-SU-2017:1174-1","title":"Security update for wireshark","description":"\nWireshark was updated to version 2.0.12, which brings several new features, enhancements\nand bug fixes.\n\nThese security issues were fixed:\n\n- CVE-2017-7700: In Wireshark the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size (bsc#1033936).\n- CVE-2017-7701: In Wireshark the BGP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-bgp.c by using a different integer data type (bsc#1033937).\n- CVE-2017-7702: In Wireshark the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation (bsc#1033938).\n- CVE-2017-7703: In Wireshark the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly (bsc#1033939).\n- CVE-2017-7704: In Wireshark the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return value (bsc#1033940).\n- CVE-2017-7705: In Wireshark the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset (bsc#1033941).\n- CVE-2017-7745: In Wireshark the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check (bsc#1033942).\n- CVE-2017-7746: In Wireshark the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length (bsc#1033943).\n- CVE-2017-7747: In Wireshark the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree (bsc#1033944).\n- CVE-2017-7748: In Wireshark the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check (bsc#1033945).\n- CVE-2016-7179: Stack-based buffer overflow in epan/dissectors/packet-catapult-dct2000.c in the Catapult DCT2000 dissector in Wireshark allowed remote attackers to cause a denial of service (application crash) via a crafted packet (bsc#998963).\n- CVE-2016-9376: In Wireshark the OpenFlow dissector could crash with memory exhaustion, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-openflow_v5.c by ensuring that certain length values were sufficiently large (bsc#1010735).\n- CVE-2016-9375: In Wireshark the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful (bsc#1010740).\n- CVE-2016-9374: In Wireshark the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable (bsc#1010752).\n- CVE-2016-9373: In Wireshark the DCERPC dissector could crash with a use-after-free, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dcerpc-nt.c and epan/dissectors/packet-dcerpc-spoolss.c by using the wmem file scope for private strings (bsc#1010754).\n- CVE-2016-7175: epan/dissectors/packet-qnet6.c in the QNX6 QNET dissector in Wireshark mishandled MAC address data, which allowed remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet (bsc#998761).\n- CVE-2016-7176: epan/dissectors/packet-h225.c in the H.225 dissector in Wireshark called snprintf with one of its input buffers as the output buffer, which allowed remote attackers to cause a denial of service (copy overlap and application crash) via a crafted packet (bsc#998762).\n- CVE-2016-7177: epan/dissectors/packet-catapult-dct2000.c in the Catapult DCT2000 dissector in Wireshark did not restrict the number of channels, which allowed remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet (bsc#998763).\n- CVE-2016-7180: epan/dissectors/packet-ipmi-trace.c in the IPMI trace dissector in Wireshark did not properly consider whether a string is constant, which allowed remote attackers to cause a denial of service (use-after-free and application crash) via a crafted packet (bsc#998800).\n- CVE-2016-7178: epan/dissectors/packet-umts_fp.c in the UMTS FP dissector in Wireshark did not ensure that memory is allocated for certain data structures, which allowed remote attackers to cause a denial of service (invalid write access and application crash) via a crafted packet (bsc#998964).\n- CVE-2017-6014: In Wireshark a crafted or malformed STANAG 4607 capture file will cause an infinite loop and memory exhaustion. If the packet size field in a packet header is null, the offset to read from will not advance, causing continuous attempts to read the same zero length packet. This will quickly exhaust all system memory (bsc#1025913).\n- CVE-2017-5596: In Wireshark the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow (bsc#1021739).\n- CVE-2017-5597: In Wireshark the DHCPv6 dissector could go into a large loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dhcpv6.c by changing a data type to avoid an integer overflow (bsc#1021739).\n","status":"published","published":"2017-05-04T10:03:13Z","modified":"2026-02-04T03:40:48.185799Z","updated_at":"2026-11-02T15:53:43.83457Z"},{"id":"SUSE-SU-2017:1442-1","title":"Security update for wireshark","description":"\nWireshark was updated to version 2.2.6, which brings several new features, enhancements\nand bug fixes.\n\nThses security issues were fixed:\n\n- CVE-2017-7700: In Wireshark the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size (bsc#1033936)\n- CVE-2017-7701: In Wireshark the BGP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-bgp.c by using a different integer data type (bsc#1033937)\n- CVE-2017-7702: In Wireshark the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation (bsc#1033938)\n- CVE-2017-7703: In Wireshark the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly (bsc#1033939)\n- CVE-2017-7704: In Wireshark the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return value (bsc#1033940)\n- CVE-2017-7705: In Wireshark the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset (bsc#1033941)\n- CVE-2017-7745: In Wireshark the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check (bsc#1033942)\n- CVE-2017-7746: In Wireshark the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length (bsc#1033943)\n- CVE-2017-7747: In Wireshark the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree (bsc#1033944)\n- CVE-2017-7748: In Wireshark the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check (bsc#1033945)\n- CVE-2017-6014: In Wireshark a crafted or malformed STANAG 4607 capture file will cause an infinite loop and memory exhaustion. If the packet size field in a packet header is null, the offset to read from will not advance, causing continuous attempts to read the same zero length packet. This will quickly exhaust all system memory (bsc#1025913)\n- CVE-2017-5596: In Wireshark the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow (bsc#1021739)\n- CVE-2017-5597: In Wireshark the DHCPv6 dissector could go into a large loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dhcpv6.c by changing a data type to avoid an integer overflow (bsc#1021739)\n- CVE-2016-9376: In Wireshark the OpenFlow dissector could crash with memory exhaustion, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-openflow_v5.c by ensuring that certain length values were sufficiently large (bsc#1010735)\n- CVE-2016-9375: In Wireshark the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful (bsc#1010740)\n- CVE-2016-9374: In Wireshark the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable (bsc#1010752)\n- CVE-2016-9373: In Wireshark the DCERPC dissector could crash with a use-after-free, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dcerpc-nt.c and epan/dissectors/packet-dcerpc-spoolss.c by using the wmem file scope for private strings (bsc#1010754)\n- CVE-2016-7180: epan/dissectors/packet-ipmi-trace.c in the IPMI trace dissector in Wireshark did not properly consider whether a string is constant, which allowed remote attackers to cause a denial of service (use-after-free and application crash) via a crafted packet (bsc#998800)\n- CVE-2016-7179: Stack-based buffer overflow in epan/dissectors/packet-catapult-dct2000.c in the Catapult DCT2000 dissector in Wireshark allowed remote attackers to cause a denial of service (application crash) via a crafted packet (bsc#998963)\n- CVE-2016-7178: epan/dissectors/packet-umts_fp.c in the UMTS FP dissector in Wireshark did not ensure that memory is allocated for certain data structures, which allowed remote attackers to cause a denial of service (invalid write access and application crash) via a crafted packet (bsc#998964)\n- CVE-2016-7177: epan/dissectors/packet-catapult-dct2000.c in the Catapult DCT2000 dissector in Wireshark did not restrict the number of channels, which allowed remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet (bsc#998763)\n- CVE-2016-7176: epan/dissectors/packet-h225.c in the H.225 dissector in Wireshark called snprintf with one of its input buffers as the output buffer, which allowed remote attackers to cause a denial of service (copy overlap and application crash) via a crafted packet (bsc#998762)\n- CVE-2016-7175: epan/dissectors/packet-qnet6.c in the QNX6 QNET dissector in Wireshark mishandled MAC address data, which allowed remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet (bsc#998761)\n- CVE-2016-6354: Heap-based buffer overflow in the yy_get_next_buffer function in Flex might have allowed context-dependent attackers to cause a denial of service or possibly execute arbitrary code via vectors involving num_to_read (bsc#990856).\n","status":"published","published":"2017-05-30T11:22:49Z","modified":"2026-02-04T04:33:08.873397Z","updated_at":"2026-11-02T15:53:43.83457Z"}]}}