CVE-2022-3703 json
ETIC Telecom Remote Access Server Insufficient Verification of Data Authenticity
published 3y ago modified 4mo ago also EUVD-2022-43061
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
All versions of ETIC Telecom Remote Access Server (RAS) 4.5.0 and prior’s web portal is vulnerable to accepting malicious firmware packages that could provide a backdoor to an attacker and provide privilege escalation to the device.
Patch / fix
Is CVE-2022-3703 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-307-01 updated cvss 7.6
ETIC Telecom Remote Access Server (RAS) (Update B)
-
ETIC Telecom RAS <4.5.0affected: mitigation “For the installed devices, ETIC Telecom recommends:” etictelecom.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- ETIC Telecom Remote Access Server (RAS)
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-307-01
patch, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-3703
- NVD CVE-2022-3703
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.