CVE-2022-2104
No exploitation reported by the sources we read.
- Published2022-06-24
- Fixed in1.25.3 · 1.24.8 · 1.23.21
- WeaknessCWE-269
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The www-data (Apache web server) account is configured to run sudo with no password for many commands (including /bin/sh and /bin/bash).
Timeline
dates in UTC- 2022-06-2415:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-2104?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-2104?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.25 | ≥ 1.25.0, < 1.25.3 | 1.25.3 | NVD |
| 1.24 | ≥ 1.24.0, < 1.24.8 | 1.24.8 | NVD |
| 1.23 | ≥ 1.23.0, < 1.23.21 | 1.23.21 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Secheron SEPCOS Control and Protection Relay
SEPCOS Single Package firmware (1.23.xx feature level): All versions prior to 1.23.21 · SEPCOS Single Package firmware (1.24.xx feature level): All versions prior to 1.24.8 · SEPCOS Single Package firmware (1.25.xx feature level): All versions prior to 1.25.3
Fix
- Update Secheron sepcos control and protection relay firmware to 1.25.3 · 1.24.8 · 1.23.21
- Vendor fix CISA ICSA-22-174-03 · 3 productsSEPCOS Single Package firmware (1.25.xx feature level): Update to 1.25.3 or higher version
- Mitigation from the vendor CISA ICSA-22-174-03 · 3 productsSEPCOS Single Package firmware (1.23.xx feature level): Update to 1.23.22 or higher version
- Mitigation from the vendor CISA ICSA-22-174-03 · 3 productsSEPCOS Single Package firmware (1.24.xx feature level): Update to 1.24.8 or higher version
- Mitigation from the vendor CISA ICSA-22-174-03 · 3 productsThis version contains updates that resolve the discovered vulnerabilities for each feature level (SP1.23.xx, SP1.24.xx, and SP1.25.xx).
- Mitigation from the vendor CISA ICSA-22-174-03 · 3 productsSystem integrators and asset owners should contact a Secheron representative for further information on how to obtain updates.
- Mitigation from the vendor CISA ICSA-22-174-03 · 3 productsConfigure the network such that PLC communications are strictly limited to only the devices required to perform its functions.
Advisories and patches
- www.cisa.govMitigation
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2022-06-24
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-2104?
Is CVE-2022-2104 actively exploited?
What is the CVSS score for CVE-2022-2104?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.