Skip to main content

SICK Logistics Analytics CVE-2025-58590

HIGH
Path Traversal (CWE-22)
2025-10-06 psirt@sick.de
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach SICK Analytics web service
  2. Delivery
    Send path-traversal request
  3. Exploit
    Escape intended directory
  4. Execution
    Read sensitive files/folders
  5. Impact
    Exfiltrate disclosed information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the web/HTTP interface of an affected SICK application - Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, or Tire Analytics - against which an unauthenticated attacker submits path-traversal input (per PR:N/UI:N/AC:L); no special product feature toggle is named in the description. The primary limiting factor is deployment context: these are industrial logistics analytics products normally installed on segmented OT networks rather than the public internet, so realistic exploitation depends on the attacker first gaining access to that network segment. Impact is confined to confidentiality (file/folder disclosure); there is no integrity or availability effect, so it cannot directly modify data or disrupt operation.

Impact

The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N, base 7.5) describes a network-reachable, low-complexity, unauthenticated path-traversal (CWE-22) with high confidentiality impact and no integrity or availability impact - consistent with information disclosure rather than code execution. No EPSS score was provided in the input, and there is no CISA KEV listing or POC indicator supplied, so exploitation signals are absent: this is no public exploit identified at time of analysis. The high CVSS is driven entirely by the confidentiality-only impact under unauthenticated remote access; however, the affected products (SICK Baggage/Logistic Diagnostic/Package/Tire Analytics) are specialized industrial-logistics analytics applications typically deployed on segmented OT/ICS networks, which materially lowers real-world internet-facing exposure versus the AV:N rating. Net: a genuine, patch-worthy information-disclosure flaw for operators of these SICK products, but likely targeted/limited rather than mass-exploited given the niche ICS deployment footprint - not a broad emergency absent exploitation evidence. Key missing data: no EPSS, no confirmed KEV/POC status in the input.

Exploit ScenarioDerived

An attacker with network access to the web interface of a SICK Analytics application sends crafted requests containing directory-traversal sequences to read files and enumerate folders outside the intended web root, harvesting sensitive data such as configuration or credential material. Because the CVSS vector is PR:N/UI:N, no authentication or user interaction is required, only reachability of the service. No public exploit was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 18, 2026

Path traversal in SICK Logistics Analytics products allows unauthenticated remote attackers to enumerate and retrieve files or folders outside intended web paths, disclosing sensitive information. The affected products identified by CPE are SICK Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics, with wildcard version entries indicating all represented versions are in scope; CVSS 3.1 base score is 7.5 with high confidentiality impact but no integrity or availability impact. No public exploit was identified at time of analysis, and the main practical barrier is that these industrial logistics products are typically deployed on segmented OT networks rather than the public internet.

RemediationAI

No exact fixed version is specified in the provided data, so consult SICK advisory SCA-2025-0010 (https://www.sick.com/.well-known/csaf/white/2025/sca-2025-0010.json and https://www.sick.com/.well-known/csaf/white/2025/sca-2025-0010.pdf) for the vendor-released fix and upgrade affected instances as directed. Until patched, restrict network access to the web/HTTP interfaces of Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics to trusted OT segments and administrative hosts; this reduces exposure but requires maintaining accurate network segmentation. Place the interfaces behind a reverse proxy or WAF that canonicalizes paths and rejects encoded traversal sequences such as ../, %2e%2e, and double-encoded variants, with the trade-off of possible false positives and bypass if rules are not tuned; a WAF is not a substitute for patching. Disable directory listing or default content where the product permits it, run the services with least-privilege filesystem permissions, and monitor web logs for folder/file enumeration and path-traversal patterns.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected SICK products are industrial logistics analytics web applications. The supplied CPE entries cover SICK Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics using wildcard version fields, so the data does not define a fixed-version boundary. CWE-22 describes the root cause: the application accepts user-controlled folder or file paths and fails to canonicalize or constrain them to an intended directory, allowing traversal sequences and folder/file brute-forcing to expose files outside the intended web content. The CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N indicates network-reachable, low-complexity, unauthenticated exploitation with high confidentiality impact and no integrity or availability effect, consistent with information disclosure rather than code execution or data modification.

Know when Baggage Analytics gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network path traversal reads arbitrary files (PR:N, AV:N, AC:L), yielding high confidentiality disclosure with no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionNVD

It's possible to brute force folders and files, what can be used by an attacker to steal sensitve information.

Executive ViewAI

Why It Matters

SICK Logistics Analytics products-Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics-present a confidentiality risk because files or folders outside intended web paths may be exposed to remote actors. These products are often deployed in segmented OT environments, which limits practical exposure, but any broadly reachable or internet-facing instance could disclose sensitive logistics and operational information. No public exploit was identified at time of analysis, and no vendor-released patch was identified at time of analysis.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; restrict affected web interfaces to trusted administrative networks or VPN, enforce OT segmentation and network allowlists, monitor for path traversal or file-retrieval attempts, and apply WAF or virtual patching rules where feasible; contact SICK for advisory and patch timeline.

Threat Intelligence Overview

EPSS Score
0.5%
Top 56% exploitable
Prevalence
Low
niche SICK industrial logistics analytics software, OT/ICS deployment only
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Affected Products (CPE)NVD

cpe:2.3:a:sick:baggage_analytics:*:*:*:*:*:*:*:*
cpe:2.3:a:sick:logistic_diagnostic_analytics:*:*:*:*:*:*:*:*
cpe:2.3:a:sick:package_analytics:*:*:*:*:*:*:*:*
cpe:2.3:a:sick:tire_analytics:*:*:*:*:*:*:*:*
CVE-2025-58587 CRITICAL
9.8 Oct 06

Credential brute-force and password guessing against the login interfaces of SICK Analytics products (Baggage, Enterpris

CVE-2025-49184 HIGH
7.5 Jun 12

A information disclosure vulnerability (CVSS 7.5). High severity vulnerability requiring prompt remediation.

CVE-2025-9914 HIGH
7.5 Oct 06

SICK Analytics products (Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics) allow

CVE-2025-58591 HIGH
7.5 Oct 06

Unauthenticated path traversal in SICK's industrial analytics platforms (Baggage Analytics, Logistic Diagnostic Analytic

CVE-2025-58585 HIGH
7.5 Oct 06

Unauthenticated information disclosure in SICK Analytics products (Baggage Analytics, Logistic Diagnostic Analytics, Pac

CVE-2025-58584 HIGH
7.5 Oct 06

Credential exposure in SICK's Baggage, Enterprise, Logistic Diagnostic, Package, and Tire Analytics applications occurs

CVE-2025-58589 MEDIUM
6.5 Oct 06

Authenticated users of SICK Baggage Analytics, Logistic Diagnostic Analytics, Package Analytics, and Tire Analytics can

CVE-2025-9913 MEDIUM
6.1 Oct 06

A cross-site scripting flaw (CWE-79) in the web dashboards of SICK's industrial analytics products - Baggage Analytics,

CVE-2025-58586 MEDIUM
5.3 Oct 06

SICK Analytics applications (Baggage, Enterprise, Logistic Diagnostic, Package, and Tire) expose username enumeration th

CVE-2025-49186 MEDIUM
5.3 Jun 12

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short tim

CVE-2025-58579 MEDIUM
5.3 Oct 06

Unauthenticated user enumeration in SICK Analytics products allows remote attackers to query an endpoint without credent

CVE-2025-49193 MEDIUM
4.2 Jun 12

The application fails to implement several security headers. These headers help increase the overall security level of t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy