{"url":"http://public2.vulnerablecode.io/api/packages/401046?format=json","purl":"pkg:apk/alpine/wireshark@2.4.4-r0?arch=aarch64&distroversion=v3.20&reponame=community","type":"apk","namespace":"alpine","name":"wireshark","version":"2.4.4-r0","qualifiers":{"arch":"aarch64","distroversion":"v3.20","reponame":"community"},"subpath":"","is_vulnerable":false,"next_non_vulnerable_version":"2.4.5-r0","latest_non_vulnerable_version":"4.2.5-r0","affected_by_vulnerabilities":[],"fixing_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/105269?format=json","vulnerability_id":"VCID-jc8e-rgaz-mfay","summary":"In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the IxVeriWave file parser could crash. This was addressed in wiretap/vwr.c by correcting the signature timestamp bounds checks.","references":[{"reference_url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5334.json","reference_id":"","reference_type":"","scores":[{"value":"5.9","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"}],"url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5334.json"},{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5334","reference_id":"","reference_type":"","scores":[{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.7547","published_at":"2026-06-04T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.75499","published_at":"2026-06-05T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.75503","published_at":"2026-06-06T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.75493","published_at":"2026-06-07T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.7548","published_at":"2026-06-08T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.75505","published_at":"2026-06-09T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5334"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"4.3","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534361","reference_id":"1534361","reference_type":"","scores":[],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534361"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/401046?format=json","purl":"pkg:apk/alpine/wireshark@2.4.4-r0?arch=aarch64&distroversion=v3.20&reponame=community","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/wireshark@2.4.4-r0%3Farch=aarch64&distroversion=v3.20&reponame=community"}],"aliases":["CVE-2018-5334"],"risk_score":2.6,"exploitability":"0.5","weighted_severity":"5.3","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-jc8e-rgaz-mfay"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/105271?format=json","vulnerability_id":"VCID-k5rs-2vsg-ekbu","summary":"In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the JSON, XML, NTP, XMPP, and GDB dissectors could crash. This was addressed in epan/tvbparse.c by limiting the recursion depth.","references":[{"reference_url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5336.json","reference_id":"","reference_type":"","scores":[{"value":"5.9","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"}],"url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5336.json"},{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5336","reference_id":"","reference_type":"","scores":[{"value":"0.01011","scoring_system":"epss","scoring_elements":"0.77455","published_at":"2026-06-04T12:55:00Z"},{"value":"0.01011","scoring_system":"epss","scoring_elements":"0.77482","published_at":"2026-06-07T12:55:00Z"},{"value":"0.01011","scoring_system":"epss","scoring_elements":"0.77493","published_at":"2026-06-09T12:55:00Z"},{"value":"0.01011","scoring_system":"epss","scoring_elements":"0.77491","published_at":"2026-06-06T12:55:00Z"},{"value":"0.01011","scoring_system":"epss","scoring_elements":"0.77471","published_at":"2026-06-08T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5336"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"4.3","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534374","reference_id":"1534374","reference_type":"","scores":[],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534374"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/401046?format=json","purl":"pkg:apk/alpine/wireshark@2.4.4-r0?arch=aarch64&distroversion=v3.20&reponame=community","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/wireshark@2.4.4-r0%3Farch=aarch64&distroversion=v3.20&reponame=community"}],"aliases":["CVE-2018-5336"],"risk_score":2.6,"exploitability":"0.5","weighted_severity":"5.3","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-k5rs-2vsg-ekbu"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/105270?format=json","vulnerability_id":"VCID-srx9-ftsv-3kcw","summary":"In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the WCP dissector could crash. This was addressed in epan/dissectors/packet-wcp.c by validating the available buffer length.","references":[{"reference_url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5335.json","reference_id":"","reference_type":"","scores":[{"value":"5.9","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"}],"url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2018-5335.json"},{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5335","reference_id":"","reference_type":"","scores":[{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.75505","published_at":"2026-06-09T12:55:00Z"},{"value":"0.00865","scoring_system":"epss","scoring_elements":"0.7548","published_at":"2026-06-08T12:55:00Z"},{"value":"0.0087","scoring_system":"epss","scoring_elements":"0.75574","published_at":"2026-06-05T12:55:00Z"},{"value":"0.0087","scoring_system":"epss","scoring_elements":"0.75578","published_at":"2026-06-06T12:55:00Z"},{"value":"0.0087","scoring_system":"epss","scoring_elements":"0.75568","published_at":"2026-06-07T12:55:00Z"},{"value":"0.0087","scoring_system":"epss","scoring_elements":"0.75546","published_at":"2026-06-04T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2018-5335"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"4.3","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534364","reference_id":"1534364","reference_type":"","scores":[],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1534364"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/401046?format=json","purl":"pkg:apk/alpine/wireshark@2.4.4-r0?arch=aarch64&distroversion=v3.20&reponame=community","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/wireshark@2.4.4-r0%3Farch=aarch64&distroversion=v3.20&reponame=community"}],"aliases":["CVE-2018-5335"],"risk_score":2.6,"exploitability":"0.5","weighted_severity":"5.3","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-srx9-ftsv-3kcw"}],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/wireshark@2.4.4-r0%3Farch=aarch64&distroversion=v3.20&reponame=community"}