DoS attack against the Stork UI from an unauthenticated user
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ISC | Stork | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Isc | Stork | — |
Vendor Solution
Upgrade to the patched release most closely related to your current version of Stork: 2.2.1 or 2.3.1.
Vendor Workaround
Placing the Stork server behind a firewall or proxy that only allows access from trusted clients, and/or enforces input size limits, is an effective workaround.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-27598 | If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for the system running the Stork server. This issue affects Stork versions 1.0.0 through 2.3.0. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.461% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Isc
Isc stork |
|
| Vendors & Products |
Isc
Isc stork |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for the system running the Stork server. This issue affects Stork versions 1.0.0 through 2.3.0. | |
| Title | DoS attack against the Stork UI from an unauthenticated user | |
| Weaknesses | CWE-779 CWE-789 |
|
| References |
| |
| Metrics |
cvssV3_1
|