svakom CVE Vulnerabilities & Metrics

Focus on svakom vulnerabilities and metrics.

Last updated: 27 Apr 2025, 22:25 UTC

About svakom Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with svakom. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total svakom CVEs: 6
Earliest CVE date: 08 Feb 2021, 02:15 UTC
Latest CVE date: 07 Nov 2024, 18:15 UTC

Latest CVE reference: CVE-2020-11919

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 4

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical svakom CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 2.43

Max CVSS: 10.0

Critical CVEs (≥9): 1

CVSS Range vs. Count

Range Count
0.0-3.9 4
4.0-6.9 1
7.0-8.9 0
9.0-10.0 1

CVSS Distribution Chart

Top 5 Highest CVSS svakom CVEs

These are the five CVEs with the highest CVSS scores for svakom, sorted by severity first and recency.

All CVEs for svakom

CVE-2020-11919 svakom vulnerability CVSS: 0 07 Nov 2024, 18:15 UTC

An issue was discovered in Siime Eye 14.1.00000001.3.330.0.0.3.14. There is no CSRF protection.

CVE-2020-11918 svakom vulnerability CVSS: 0 07 Nov 2024, 18:15 UTC

An issue was discovered in Siime Eye 14.1.00000001.3.330.0.0.3.14. When a backup file is created through the web interface, information on all users, including passwords, can be found in cleartext in the backup file. An attacker capable of accessing the web interface can create the backup file.

CVE-2020-11917 svakom vulnerability CVSS: 0 07 Nov 2024, 18:15 UTC

An issue was discovered in Siime Eye 14.1.00000001.3.330.0.0.3.14. It uses a default SSID value, which makes it easier for remote attackers to discover the physical locations of many Siime Eye devices, violating the privacy of users who do not wish to disclose their ownership of this type of device. (Various resources such as wigle.net can be use for mapping of SSIDs to physical locations.)

CVE-2020-11916 svakom vulnerability CVSS: 0 07 Nov 2024, 18:15 UTC

An issue was discovered in Siime Eye 14.1.00000001.3.330.0.0.3.14. The password for the root user is hashed using an old and deprecated hashing technique. Because of this deprecated hashing, the success probability of an attacker in an offline cracking attack is greatly increased.

CVE-2020-11920 svakom vulnerability CVSS: 10.0 08 Feb 2021, 02:15 UTC

An issue was discovered in Svakom Siime Eye 14.1.00000001.3.330.0.0.3.14. A command injection vulnerability resides in the HOST/IP section of the NFS settings menu in the webserver running on the device. By injecting Bash commands via shell metacharacters here, the device executes arbitrary code with root privileges (all of the device's services are running as root).

CVE-2020-11915 svakom vulnerability CVSS: 4.6 08 Feb 2021, 02:15 UTC

An issue was discovered in Svakom Siime Eye 14.1.00000001.3.330.0.0.3.14. By sending a set_params.cgi?telnetd=1&save=1&reboot=1 request to the webserver, it is possible to enable the telnet interface on the device. The telnet interface can then be used to obtain access to the device with root privileges via a reecam4debug default password. This default telnet password is the same across all Siime Eye devices. In order for the attack to be exploited, an attacker must be physically close in order to connect to the device's Wi-Fi access point.