Vendor
Cougar
Products
2
CVEs
4
Across products
4
Status
Private
Products
2- 3 CVEs
- 1 CVE
Recent CVEs
4| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2014-3928 | Cri | 0.64 | 9.8 | 0.02 | Apr 3, 2017 | Cougar-LG stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain credentials. | ||
| CVE-2014-3929 | Hig | 0.49 | 7.5 | 0.02 | Apr 3, 2017 | The default configuration for Cougar-LG stores sensitive information under the web root with insufficient access control, which might allow remote attackers to obtain private ssh keys. | ||
| CVE-2014-3926 | Med | 0.40 | 6.1 | 0.01 | Mar 13, 2017 | Cross-site scripting (XSS) vulnerability in lg.cgi in Cougar LG 1.9 allows remote attackers to inject arbitrary web script or HTML via the "addr" parameter. | ||
| CVE-2024-46747 | 0.00 | — | 0.00 | Sep 18, 2024 | In the Linux kernel, the following vulnerability has been resolved: HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup report_fixup for the Cougar 500k Gaming Keyboard was not verifying that the report descriptor size was correct before accessing it |
- risk 0.64cvss 9.8epss 0.02
Cougar-LG stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain credentials.
- risk 0.49cvss 7.5epss 0.02
The default configuration for Cougar-LG stores sensitive information under the web root with insufficient access control, which might allow remote attackers to obtain private ssh keys.
- risk 0.40cvss 6.1epss 0.01
Cross-site scripting (XSS) vulnerability in lg.cgi in Cougar LG 1.9 allows remote attackers to inject arbitrary web script or HTML via the "addr" parameter.
- CVE-2024-46747Sep 18, 2024risk 0.00cvss —epss 0.00
In the Linux kernel, the following vulnerability has been resolved: HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup report_fixup for the Cougar 500k Gaming Keyboard was not verifying that the report descriptor size was correct before accessing it