Cleartext Transmission of Sensitive Information in Ormazabal products
The lack of web request control on ekorCCP and ekorRCI devices allows a potential attacker to create custom requests to execute malicious actions when a user is logged in.
- Published
- Sep 20, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- CWE-319
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · INCIBE
- 5.7
- 0.8 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| ormazabal | ekorrci firmware | cpe:2.3:o:ormazabal:ekorrci_firmware |
| ormazabal | ekorrci | cpe:2.3:h:ormazabal:ekorrci |
| ormazabal | ekorccp firmware | cpe:2.3:o:ormazabal:ekorccp_firmware |
| ormazabal | ekorccp | cpe:2.3:h:ormazabal:ekorccp |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ormazabal ekorccp firmware601j
- ormazabal ekorrci firmware601j
Versions reported by the vendor
Affected version ranges reported by the assigning authority (INCIBE). Independent of NVD's CPE analysis and usually ahead of it.
Ormazabal ekorCCP
- 601jaffected
Ormazabal ekorRCI
- 601jaffected
Same product
ormazabal: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-47558Improper Access Control in Ormazabal products39Monitor
- CVE-2022-47559Cross-Site Request Forgery in Ormazabal products35Monitor
- CVE-2022-47555Improper Neutralization of Special Elements in Ormazabal products35Monitor
- CVE-2022-47554Exposure of Sensitive Information in Ormazabal products30Monitor
- CVE-2022-47553Improper Authorization in Ormazabal products30Monitor
- CVE-2022-47556Uncontrolled Resource Consumption in Ormazabal products26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jacinto Moral Matellánfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.