CVE-2022-2662 json
Sequi PortBloque S Improper Authentication
published 4y ago modified 4mo ago also EUVD-2022-34908
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
Sequi PortBloque S has a improper authentication issues which may allow an attacker to bypass the authentication process and gain user-level access to the device.
Is CVE-2022-2662 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-228-07 updated cvss 9.6
Sequi PortBloque S
-
Sequi PortBloque Saffected: mitigation “As of August 9, 2022, Sequi has not responded to requests to work with CISA to mitigate these vulnerabilities. Users of this affected product should contact Sequi for additional information.”
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.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Sequi PortBloque S
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-228-07
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-2662
- NVD CVE-2022-2662
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.