CVE-2022-47557
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 · uneditedVulnerability in ekorCCP and ekorRCI that could allow an attacker with access to the network where the device is located to decrypt the credentials of privileged users, and subsequently gain access to the system to perform malicious actions.
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 confidenceA vulnerability in ekorCCP and ekorRCI allows an attacker with network access to decrypt credentials of privileged users. The vulnerability appears to involve improper encryption or key management for stored credentials, enabling credential theft and subsequent unauthorized system access.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 installed firmware versionAccess the device management interface or system information panel to retrieve the current firmware version. Common methods include logging into the device console, checking system status pages, or using vendor-provided diagnostic tools to query the firmware version.Affected if The firmware version is exactly 601j (Ormazabal Ekorrci or Ekorccp)
-
Confirm product is Ekorrci or EkorccpVerify that the affected system is specifically the Ormazabal Ekorrci or Ekorccp platform by checking the system identification, product name, or device model information in the management interface.Affected if The product is identified as Ormazabal Ekorrci or Ormazabal Ekorccp running firmware 601j
-
Assess network exposureReview network configuration, firewall rules, and access control lists to determine if the device management interface or credential storage systems are accessible from untrusted networks. Check for direct IP exposure or VPN status.Affected if The device has network accessibility from untrusted networks without proper segmentation
-
Review credential storage configurationExamine the system configuration files, credential storage settings, or encryption parameters within the device management interface to identify how credentials are stored and which encryption mechanism is in use.Affected if Credential storage uses the default encryption mechanism without custom key management enabled
-
Check for privileged user accountsReview the user management section to identify privileged accounts (administrator, operator, or superuser roles) that would be targets for credential theft via this vulnerability.Affected if Privileged user accounts exist in the system
A user is affected if they are running Ormazabal Ekorrci or Ekorccp firmware version 601j with the device network-accessible and credential storage using the vulnerable encryption mechanism.
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 dataImplement network segmentation to limit exposure, apply vendor patches when available, and review credential storage mechanisms. Consider rotating affected credentials as a precautionary measure.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47557 — 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-47557 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