CVE-2022-2103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn attacker with weak credentials could access the TCP port via an open FTP port, allowing an attacker to read sensitive files and write to remotely executable directories.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn FTP service with weak credentials allows attackers to access the TCP port and authenticate, enabling reading of sensitive files on the system and writing files to directories that permit execution, leading to potential remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.23.0, < 1.23.21>= 1.24.0, < 1.24.8>= 1.25.0, < 1.25.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Secheron Sepcos device in environmentLocate Sepcos Control And Protection Relay devices on the network by checking for FTP services on common ports (21/TCP) or identifying the device through network scans, asset inventories, or device discovery logs.Affected if A Secheron Sepcos device with FTP service accessible on the network is present.
-
Check installed firmware versionAccess the device management interface or use SNMP/management protocols to query the firmware version. Compare the installed version against the affected ranges: 1.23.0 to 1.23.20, 1.24.0 to 1.24.7, and 1.25.0 to 1.25.2.Affected if The firmware version falls within any of the affected ranges listed.
-
Verify FTP service statusCheck if the FTP service is enabled and running on the device by scanning port 21/TCP or reviewing the device service configuration via its management interface.Affected if FTP service is enabled and accepting connections on the device.
-
Test FTP authentication with default credentialsAttempt to authenticate to the FTP service using known default credential combinations for Sepcos devices, or verify whether anonymous access is permitted.Affected if Default credentials are accepted or anonymous FTP access is allowed.
-
Inspect FTP directory access permissionsAfter authenticating, enumerate accessible directories and verify whether the FTP user has write access to directories that permit script or executable file execution.Affected if The authenticated FTP session can write to directories that allow execution of uploaded files.
You are affected if you have a Secheron Sepcos device running vulnerable firmware (versions 1.23.x before 1.23.21, 1.24.x before 1.24.8, or 1.25.x before 1.25.3) with FTP enabled and accessible using weak or default credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.23.211.24.81.25.3
Replace weak/default credentials with strong, complex passwords and disable anonymous FTP access; if this is a product vulnerability rather than configuration, apply vendor patches and restrict FTP access to trusted IP addresses via firewall rules.
Upgrade to firmware version 1.23.21 or later (for 1.23.x branch), 1.24.8 or later (for 1.24.x branch), or 1.25.3 or later (for 1.25.x branch)
- Identify the current firmware version running on the Sepcos Control And Protection Relay device
- Determine which firmware branch (1.23.x, 1.24.x, or 1.25.x) the device is currently running
- Obtain the firmware upgrade from the official vendor (ABB/Siemens Grid Automation division) through their support channels
- Review all upgrade documentation and release notes before proceeding
- Apply the firmware upgrade following vendor-provided instructions, ensuring stable power during the update process
- After upgrade, verify the new firmware version matches or exceeds the minimum fixed version (1.23.21 for 1.23.x branch, 1.24.8 for 1.24.x branch, or 1.25.3 for 1.25.x branch)
- Change default/weak credentials to strong passwords as an additional security measure
- Verify that the FTP service is properly secured or disabled if not required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data