Dell ECS EUVD-2022-54113

The only hard prerequisite is network reachability to a Dell ECS 3.5.x (before 3.5.1.7) or 3.6.x (before 3.6.2.4) instance whose IAM-governed endpoints are exposed to the attacker; the CVSS vector AV:N/AC:L/PR:N/UI:N confirms no authentication, no user interaction, and low complexity against default configurations. Impact is limited to unauthorized READ access (C:H, I:N, A:N) - the attacker cannot modify data or affect availability through this flaw. The practical limiting factor is exposure: an ECS deployment whose API/management interfaces are confined to an internal or segmented storage network is only reachable by attackers who already have access to that network, sharply reducing real-world exploitability despite the network attack vector.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5 High) describes an easy, network-reachable, unauthenticated read-only breach: high confidentiality impact but zero integrity or availability impact. Countervailing signals lower the real-world priority: EPSS is 0.03% (10th percentile), no POC is known, the vulnerability is not in CISA KEV, and CISA's SSVC framework rates Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial'. The 'partial' technical impact and 'no' automatable rating are consistent with a data-disclosure bug that does not grant full system control and is not trivially scriptable across many targets. Net assessment: a genuine confidentiality risk worth patching on a normal cycle, but not an emergency - this is a high-CVSS issue whose secondary signals (EPSS, SSVC, no exploit) point to low active-exploitation likelihood rather than mass exploitation. No conflicting data was found; the network/unauthenticated vector in the description agrees with the CVSS vector.

An attacker with network reachability to an exposed Dell ECS 3.5/3.6 endpoint sends crafted requests to an IAM-governed data path without supplying valid credentials, and the authorization check fails to block them, returning stored objects or configuration/metadata they are not entitled to see. Given AV:N/AC:L/PR:N/UI:N, this requires only network access and no authentication, interaction, or elevated privileges - though no public exploit code is currently known, so exploitation would require independent research.