Remote crash via unreleased alarm-event UUIDs
Published Jul 19, 2021 · Updated Aug 4, 2024
Memory leak in sim-organizer.c in AlienVault OSSIM 5.0 allows remote attackers to crash the system by generating many alarm events. In the alarm-event path, sim_uuid_new() allocates event->backlog_id, but sim_event_unref() runs without releasing that allocation. Repeated alarm events steadily consume memory; no authentication or user interaction is required, and the reported consequence is an availability-only system crash.
Summary
What happened
Memory leak in sim-organizer.c in AlienVault OSSIM 5.0 allows remote attackers to crash the system by generating many alarm events. In the alarm-event path, sim_uuid_new() allocates event->backlog_id, but sim_event_unref() runs without releasing that allocation. Repeated alarm events steadily consume memory; no authentication or user interaction is required, and the reported consequence is an availability-only system crash.
The record
- CVE
- CVE-2020-22650
- Published
- Jul 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo