SICK Analytics CVE-2025-58585

Exploitation requires network reachability to the affected SICK Analytics application (Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, or Tire Analytics) and the ability to send requests to its web endpoints; per CVSS PR:N/UI:N no authentication or user interaction is needed, so default-configured instances expose the sensitive endpoints to any party that can reach them on the network. The primary limiting factor is network exposure: these are specialized industrial/logistics products normally placed on internal or OT networks, so realistic risk depends on whether the instance is reachable by the attacker (e.g., flat networks, VPN access, or inadvertent internet exposure); impact is confined to disclosure of sensitive information, with no integrity or availability effect.

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N, base 7.5) is internally consistent: a network-reachable, low-complexity, unauthenticated flaw with high confidentiality impact and no integrity or availability effect, which matches CWE-497 (exposure of sensitive system information) and the description of multiple unauthenticated endpoints leaking sensitive data. No EPSS score, KEV listing, or POC indicator was supplied in the input, so exploitation likelihood cannot be quantified from the data; there is no public exploit identified at time of analysis. The signals do not conflict, but note that the real-world priority is bounded by the affected products - SICK Baggage/Logistic Diagnostic/Package/Tire Analytics are specialized industrial/logistics analytics applications, typically deployed on OT or segmented networks rather than the open internet, so 'AV:N' reflects network reachability within reach of the attacker rather than guaranteed internet exposure. Impact is information disclosure only (C:H, I:N, A:N): no code execution or service disruption, so this is a genuine confidentiality concern for operators of these specific SICK products but not a mass-exploitation candidate absent evidence of exposure. EPSS is not available, so widespread-versus-targeted exploitation cannot be inferred.

An attacker with network access to a SICK Analytics instance (e.g., an adjacent OT/logistics network segment) sends requests directly to the unauthenticated endpoints and retrieves sensitive application or system information without any credentials or user interaction. No public exploit is identified, but the low attack complexity means a simple HTTP client or browser is sufficient to enumerate the exposed endpoints.