riello-ups CVE Vulnerabilities & Metrics

Focus on riello-ups vulnerabilities and metrics.

Last updated: 08 Mar 2025, 23:25 UTC

About riello-ups Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with riello-ups. 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 riello-ups CVEs: 7
Earliest CVE date: 03 Jul 2019, 17:15 UTC
Latest CVE date: 25 Sep 2024, 01:15 UTC

Latest CVE reference: CVE-2024-8878

Rolling Stats

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

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): -50.0%

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

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical riello-ups CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 1.43

Max CVSS: 10.0

Critical CVEs (≥9): 1

CVSS Range vs. Count

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

CVSS Distribution Chart

Top 5 Highest CVSS riello-ups CVEs

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

All CVEs for riello-ups

CVE-2024-8878 riello-ups vulnerability CVSS: 0 25 Sep 2024, 01:15 UTC

The password recovery mechanism for the forgotten password in Riello Netman 204 allows an attacker to reset the admin password and take over control of the device.This issue affects Netman 204: through 4.05.

CVE-2024-8877 riello-ups vulnerability CVSS: 0 25 Sep 2024, 01:15 UTC

Improper neutralization of special elements results in a SQL Injection vulnerability in Riello Netman 204. It is only limited to the SQLite database of measurement data.This issue affects Netman 204: through 4.05.

CVE-2022-47893 riello-ups vulnerability CVSS: 0 03 Oct 2023, 12:15 UTC

There is a remote code execution vulnerability that affects all versions of NetMan 204. A remote attacker could upload a firmware file containing a webshell, that could allow him to execute arbitrary code as root.

CVE-2022-47892 riello-ups vulnerability CVSS: 0 03 Oct 2023, 12:15 UTC

All versions of NetMan 204 could allow an unauthenticated remote attacker to read a file (config.cgi) containing sensitive information, like credentials.

CVE-2022-47891 riello-ups vulnerability CVSS: 0 03 Oct 2023, 12:15 UTC

All versions of NetMan 204 allow an attacker that knows the MAC and serial number of the device to reset the administrator password via the legitimate recovery function.

CVE-2022-3372 riello-ups vulnerability CVSS: 0 21 Jun 2023, 13:15 UTC

There is a CSRF vulnerability on Netman-204 version 02.05. An attacker could manage to change administrator passwords through a Cross Site Request Forgery due to the lack of proper validation on the CRSF token. This vulnerability could allow a remote attacker to access the administrator panel, being able to modify different parameters that are critical for industrial operations.

CVE-2017-6900 riello-ups vulnerability CVSS: 10.0 03 Jul 2019, 17:15 UTC

An issue was discovered in Riello NetMan 204 14-2 and 15-2. The issue is with the login script and wrongpass Python script used for authentication. When calling wrongpass, the variables $VAL0 and $VAL1 should be enclosed in quotes to prevent the potential for Bash command injection. Further to this, VAL0 and VAL1 should be sanitised to ensure they do not contain malicious characters. Passing it the username of '-' will cause it to time out and log the user in because of poor error handling. This will log the attacker in as an administrator where the telnet / ssh services can be enabled, and the credentials for local users can be reset. Also, login.cgi accepts the username as a GET parameter, so login can be achieved by browsing to the /cgi-bin/login.cgi?username=-%20a URI.