CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
9.7 | $0-$5k | 0.00 |
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 product 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.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB 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.): 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Media Server 1.8.1-2876
Timeline
01/05/2022 🔍07/28/2022 🔍
07/28/2022 🔍
08/28/2022 🔍
Sources
Vendor: synology.comAdvisory: SA_20_24
Status: Confirmed
CVE: CVE-2022-22683 (🔍)
Entry
Created: 07/28/2022 01:55 PMUpdated: 08/28/2022 10:00 AM
Changes: 07/28/2022 01:55 PM (50), 08/28/2022 10:00 AM (9)
Complete: 🔍
Cache ID: 44:D48:40
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,
Thomas Schittli
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!