In Eclipse Milo versions 1.0.0 through 1.1.4, monitored-item quota accounting is not exception-safe: if item creation fails with an unchecked error, the server-global reservation is not restored. Deeply nested PubSub ExtensionObjects in a `CreateMonitoredItems` event filter can trigger a `StackOverflowError` during decoding, allowing an unauthenticated remote client to exhaust a finite global monitored-item quota and prevent all clients from creating new monitored items until restart. Existing monitored items and other server functions remain unaffected.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
Low
Partial disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Eclipse Milo
cpe:2.3:a:eclipse:milo:*:*:*:*:*:*:*:*
|
1.0.0
|
1.1.5
|
References 4
https://github.com/eclipse-milo/milo/commit/587e35669f519b2d7f6d850a5f86ee5a76c…
emo@eclipse.org
https://github.com/eclipse-milo/milo/commit/5f3f6da2a5ea80682e1da7c58f7a1870b09…
emo@eclipse.org
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/182
emo@eclipse.org
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/598
emo@eclipse.org