SICK Enterprise Analytics
CVE-2025-58582
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach login endpoint over network
-
DeliverySubmit failed login with oversized POST body
-
ExploitUnvalidated payload written to logs
-
ExecutionRepeat to exhaust storage/memory
-
ImpactService availability denied
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special configuration is required: the flaw is reachable against the standard login functionality of SICK Enterprise Analytics. The specific precondition is simply that an attacker can reach the authentication/login POST endpoint over the network and submit a request with incorrect credentials - the application logs the failed-attempt POST data without validating or bounding its size (CWE-770). Exploitation is limited only by network reachability to the login interface; because PR:N and UI:N, no authentication or user interaction is needed. Realistic limiting factors are therefore network-level controls (whether the login endpoint is internet-exposed versus segmented behind ICS/OT network boundaries) and any upstream request-size limits imposed by a reverse proxy or WAF, which could blunt the oversized-payload vector. |
| Impact | This is a genuine but moderate-priority availability issue, not an overstated high-CVSS finding. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) legitimately supports remote, unauthenticated, low-complexity exploitation with no user interaction, and the sole impact is availability (C:N/I:N/A:H) - consistent with CWE-770 (unbounded resource allocation) and the 'Denial Of Service' tag. However, supporting signals temper the urgency: EPSS is only 0.55% (44th percentile), the CVE is NOT in CISA KEV, and no public exploit code is referenced, so there is no evidence of active or widespread exploitation. The attack is trivially performed (sending an oversized POST to a failed-login endpoint that logs unvalidated data), but the payoff is limited to service/log-storage exhaustion rather than code execution or data compromise. No SSVC decision data was provided in the input, so automatability and technical-impact scoring cannot be cross-referenced. Net: real and easy to trigger, but low real-world exploitation pressure and bounded impact make this an important patch-when-convenient item rather than an emergency, especially given the niche ICS/analytics product footprint. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker repeatedly submits login requests with intentionally incorrect credentials but attaches extremely large, unvalidated payloads in the POST body. Each failed attempt is written to logs without size limits, progressively consuming disk, memory, or logging-pipeline resources until the SICK Enterprise Analytics service degrades or becomes unavailable. No public proof-of-concept is referenced, but the technique requires only an HTTP client and knowledge of the login endpoint. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Unbounded logging in SICK Enterprise Analytics allows unauthenticated remote attackers to exhaust server resources by submitting oversized POST payloads to the login endpoint. When a login attempt fails, the application writes the request data to a log without validating or bounding its size (CWE-770), so repeated or very large submissions can flood logs and drive disk or memory consumption, degrading or halting the service. The flaw is network-reachable with no authentication or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), but impact is limited to availability. Exploitation status: no public exploit identified at time of analysis, and EPSS is low at 0.55% (44th percentile), consistent with a moderate-priority availability issue rather than an actively exploited one.
RemediationAI
There is no confirmed vendor-released patch version in the available data, so the first action is to consult SICK PSIRT advisory SCA-2025-0010 (https://www.sick.com/.well-known/csaf/white/2025/sca-2025-0010.json and the PDF at https://www.sick.com/.well-known/csaf/white/2025/sca-2025-0010.pdf, or https://sick.com/psirt) for the exact fixed release and apply it as soon as it is published. Until a patch is applied, deploy compensating controls that blunt the oversized-payload vector: enforce a strict request-body-size limit on the login POST endpoint at a reverse proxy or WAF - the trade-off is that a limit set too low may reject legitimate login submissions, so tune it against observed normal request sizes. Rate-limit failed login attempts per source IP or session, accepting the risk of locking out legitimate users behind shared NAT. Restrict network access to the Enterprise Analytics login interface using segmentation and firewall rules so it is reachable only from trusted administrative networks, which is the most effective control for an ICS/OT-deployed product but requires changes to network architecture. Additionally, cap application log file size and enable log rotation with alerting on abnormal growth so that a successful flooding attempt is detected and disk exhaustion is bounded rather than allowed to take the service down; these measures reduce but do not eliminate the denial-of-service risk and should be treated as interim only. Follow the referenced CISA ICS recommended practices and SICK operating guidelines for cybersecurity when hardening OT deployments.
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 component is the authentication/login POST handler of SICK Enterprise Analytics. Its design flaw maps to CWE-770 (Allocation of Resources Without Limits or Throttling): failed-login events are recorded to a log file, but the payload of the offending POST request is neither size-validated nor truncated before being written. An attacker who can reach the login interface can therefore dictate the volume of data appended to application logs per request - a classic log-amplification / resource-exhaustion pattern. Because the CVSS vector is PR:N and UI:N, no valid session or victim interaction is needed; the only precondition is network reachability to the login endpoint, and the mechanism is entirely availability-oriented (C:N/I:N/A:H). The CPE cpe:2.3:a:sick:enterprise_analytics:*:*:*:*:*:*:*:* indicates the wildcard covers all shipping versions unless the vendor advisory narrows the range. Practical mitigations are environmental: request-body-size limits at a reverse proxy or WAF, log rotation and quota enforcement, and network segmentation that keeps the login interface off the public internet inside ICS/OT deployments.
Know when Enterprise 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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Unauthenticated network request to the login endpoint (AV:N/PR:N/UI:N) with low complexity; unbounded logging exhausts resources for availability-only impact (A:H, C:N/I:N).
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
If a user tries to login but the provided credentials are incorrect a log is created. The data for this POST requests is not validated and it’s possible to send giant payloads which are then logged.
Executive ViewAI
SICK Enterprise Analytics is affected by an unauthenticated remote denial-of-service vulnerability (CVE-2025-58582) that can exhaust server resources through oversized login requests, potentially degrading or halting the service for all users. Because no vendor patch is available, any network-reachable attacker could disrupt analytics operations, impacting employees and business processes that depend on the platform. Leadership should prioritize reducing network exposure and monitoring resource consumption while awaiting a vendor fix.
No vendor-released patch identified at time of analysis. Interim mitigations include network segmentation, rate limiting, request size validation, log rotation with size caps, WAF virtual patching, and continuous resource monitoring.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Affected Products (CPE)NVD
More in Enterprise Analytics
View allA information disclosure vulnerability (CVSS 7.5). High severity vulnerability requiring prompt remediation.
SICK Enterprise Analytics exposes an API endpoint that accepts POST requests and writes attacker-supplied content into a
SICK Enterprise Analytics exposes a login-protected H2 database used for caching, and the login page renders with the us
SICK Enterprise Analytics returns full application stack traces to authenticated users who trigger an error, disclosing
An authenticated user who already possesses account-creation authorization can issue unlimited POST requests to the SICK
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB