Synology Media Server prior 1.8.1-2876 CGI buffer overflow
|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.
A vulnerability, which was classified as very critical, has been found in Synology Media Server. This issue affects an unknown function of the component CGI Handler. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The program copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Buffer copy without checking size of input ('Classic Buffer Overflow') vulnerability in cgi component in Synology Media Server before 1.8.1-2876 allows remote attackers to execute arbitrary code via unspecified vectors.
The weakness was disclosed 07/28/2022 as SA_20_24. It is possible to read the advisory at synology.com. The identification of this vulnerability is CVE-2022-22683 since 01/05/2022. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/28/2022).
Upgrading to version 1.8.1-2876 eliminates this vulnerability.
CVSSv3VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.7
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 10.0
CNA Vector (Synology Inc.): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Buffer overflow
CWE: CWE-120 / CWE-119
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: Media Server 1.8.1-2876
Timeline01/05/2022 CVE reserved
07/28/2022 +203 days Advisory disclosed
07/28/2022 +0 days VulDB entry created
08/28/2022 +31 days VulDB last update
CVE: CVE-2022-22683 (🔒)
EntryCreated: 07/28/2022 01:55 PM
Updated: 08/28/2022 10:00 AM
Changes: 07/28/2022 01:55 PM (50), 08/28/2022 10:00 AM (9)
Why does one have to search for the status of a vulnerability in the small text of vuldb.com (e.g. 'Upgrading to version 1.8.1-2876 eliminates this vulnerability')?
Wouldn't it be extremely useful to have the status (e.g. Unconfirmed, Confirmed, Resolved, ...) in the colored information in your header just by the colored areas of "CVSS Meta Temp Score" , "Current Exploit Price (≈)" and "CTI Interest Score"?
Thanks a lot, kind regards,
Do you need the next level of professionalism?
Upgrade your account now!