CVE-2022-49038

CVE-2022-49038 is a high-severity vulnerability in Synology Drive Client with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-829.

Key facts

Description

Inclusion of functionality from untrusted control sphere vulnerability in OpenSSL DLL component in Synology Drive Client before 3.3.0-15082 allows local users to execute arbitrary code via unspecified vectors.

Frequently asked questions

What is CVE-2022-49038?
Inclusion of functionality from untrusted control sphere vulnerability in OpenSSL DLL component in Synology Drive Client before 3.3.0-15082 allows local users to execute arbitrary code via unspecified vectors.
How severe is CVE-2022-49038?
CVE-2022-49038 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-49038 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-49038?
CVE-2022-49038 affects Synology Drive Client. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-49038?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2022-49038 have an EU (EUVD) identifier?
Yes. CVE-2022-49038 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2022-53880.
When was CVE-2022-49038 published?
CVE-2022-49038 was published on 2024-09-26 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Synology Drive Client

All CVEs affecting Synology Drive Client →

Other CWE-829 vulnerabilities

Browse all CWE-829 vulnerabilities →