CVE-2022-47555
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 · uneditedOperating system command injection in ekorCCP and ekorRCI, which could allow an authenticated attacker to execute commands, create new users with elevated privileges or set up a backdoor.
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 confidenceCommand injection vulnerability in ekorCCP and ekorRCI components allows authenticated attackers to inject operating system commands through unsanitized input, enabling arbitrary command execution, privilege escalation through new user creation, and backdoor establishment.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 firmware versionAccess the device management interface or check system information to determine the installed firmware version. For Ormazabal Ekorrci, look in the system settings or use the command-line interface to query the firmware version. For Ekorccp, locate the version information through the control panel or by examining the firmware file metadata.Affected if The installed firmware version is exactly 601j for either Ekorrci or Ekorccp component
-
Confirm presence of vulnerable componentsDetermine if the ekorCCP or ekorRCI components are installed and enabled on the device. These are specific management/control components in the Ormazabal firmware. Check the component list or running services on the affected device.Affected if Either the ekorCCP or ekorRCI component is present and running on the system
-
Verify component exposure to authenticated usersExamine the access control configuration to determine if authenticated users have access to the vulnerable command execution functions within ekorCCP or ekorRCI. Check the user role permissions and which roles can access these components.Affected if Authenticated users with standard or elevated privileges can access the command execution features of these components
-
Audit for unauthorized user accountsReview the local user database or directory service for newly created accounts that were not provisioned through normal administrative procedures. Look for accounts created after the firmware was deployed or accounts with unusual names.Affected if New user accounts exist that were not created by legitimate administrators
-
Inspect for suspicious network listeners or processesCheck for unexpected listening ports, unusual processes, or reverse shell connections that may indicate a backdoor established through the command injection vulnerability. Use netstat or similar tools to list active network connections.Affected if Unexpected processes are running or unusual network connections are established to external addresses
The environment is affected if the firmware version is exactly 601j AND the ekorCCP or ekorRCI component is present and accessible to authenticated users, particularly if combined with evidence of unauthorized account creation or suspicious network activity.
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 strict input validation and use parameterized command execution methods instead of shell command concatenation. Apply authentication and authorization controls to restrict which authenticated users can access vulnerable functions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47555 — 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-47555 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