CVE-2022-47558
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 · uneditedDevices ekorCCP and ekorRCI are vulnerable due to access to the FTP service using default credentials. Exploitation of this vulnerability can allow an attacker to modify critical files that could allow the creation of new users, delete or modify existing users, modify configuration files, install rootkits or backdoors.
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 · high confidenceThe ekorCCP and ekorRCI devices expose an FTP service that can be accessed using default credentials. An unauthenticated remote attacker can connect to this FTP service and modify critical system files, enabling creation of new user accounts, deletion or modification of existing users, alteration of configuration files, and installation of rootkits or backdoors.
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= 601j= 601jCVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the device modelCheck the device label, web interface, or system information to confirm the model is either Ormazabal Ekorrci or Ormazabal EkorccpAffected if The device is not an Ekorrci or Ekorccp model, then this CVE does not apply
-
Check firmware versionAccess the device's administrative interface or use SNMP/CLI to query the firmware version. Compare it to the affected version 601jAffected if Firmware version is exactly 601j, proceed to next check. If version differs, this specific CVE may not apply
-
Verify FTP service statusCheck if FTP service is enabled and listening on the device. This can be done by scanning the device IP for port 21 or checking the device configuration for FTP daemon settingsAffected if FTP service is disabled or not listening, the vulnerability cannot be exploited. If FTP is running and accessible, the device is potentially affected
-
Confirm default credential exposureAttempt to access the FTP service using default credentials (root/admin combinations common to these devices). If login succeeds, the device is affectedAffected if FTP accepts default credentials and grants access, the device is confirmed affected by this CVE
The device is affected if it is an Ormazabal Ekorrci or Ekorccp running firmware version 601j with FTP service enabled and accessible using 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.
From vendor dataImmediately change default credentials on the affected devices and disable or properly secure the FTP service. If the FTP service cannot be adequately secured, disable it entirely and replace with a secure file transfer protocol.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47558 — 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-47558 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