Buffalo LS210D 1.78-0.03 Firmware Update Script update_notifications.sh privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.1$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Buffalo LS210D 1.78-0.03. Affected by this vulnerability is an unknown functionality of the file /etc/init.d/update_notifications.sh of the component Firmware Update Script. The manipulation results in an unknown weakness. This vulnerability is cataloged as CVE-2023-51073. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Buffalo LS210D 1.78-0.03. It has been classified as critical. Affected is an unknown function of the file /etc/init.d/update_notifications.sh of the component Firmware Update Script. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

An issue in Buffalo LS210D v.1.78-0.03 allows a remote attacker to execute arbitrary code via the Firmware Update Script at /etc/init.d/update_notifications.sh.

The weakness was shared 01/11/2024. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2023-51073 since 12/18/2023. There are known technical details, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.2
VulDB Meta Temp Score: 7.1

VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/18/2023 🔍
01/11/2024 +24 days 🔍
01/11/2024 +0 days 🔍
06/07/2025 +512 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-51073 (🔍)
GCVE (CVE): GCVE-0-2023-51073
GCVE (VulDB): GCVE-100-250404

Entryinfo

Created: 01/11/2024 08:37
Updated: 06/07/2025 00:57
Changes: 01/11/2024 08:37 (37), 01/30/2024 10:01 (11), 06/07/2025 00:57 (15)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!