Description

ERF file parser crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.1",
  "pubDate": "2026-08-19T23:16:19.313Z",
  "pubdate": "2026-08-19T23:16:19.313Z",
  "executiveSummary": "A denial of service vulnerability exists within the ERF file parser across specific versions of the affected software. The flaw allows an unauthenticated attacker to trigger application crashes by supplying a specially crafted ERF file for parsing. Successful exploitation results in the disruption of availability for the targeted service or application parsing the malformed input. The vulnerability stems from improper handling of structural data within the ERF parsing component, leading to abnormal termination when encountering anomalous inputs. This risk threatens system reliability where untrusted ERF files are processed automatically or manually by users with standard privileges. Mitigation requires applying available software updates or patches provided by the vendor to resolve the parsing exception handling logic.",
  "technicalDetails": "The vulnerability resides within the ERF file parser component responsible for interpreting and processing ERF format data structures. The root cause involves a failure in input validation or exception handling within the parser implementation, which fails to gracefully manage unexpected, malformed, or out-of-bounds values present within the input file. When the affected software parses a maliciously constructed ERF file, it triggers a fatal runtime exception, memory corruption, or an infinite loop resulting in resource exhaustion, ultimately causing the parsing process or the host application to crash.\nThe attack vector requires an attacker to deliver a malformed ERF payload to the vulnerable system. This can occur via local file ingestion or through network-based interfaces if the application automatically processes uploaded or transmitted ERF files. No authentication or elevated privileges are required to generate the triggering input file, lowering the barrier to exploitation. Once the application attempts to read and parse the malicious structure, the vulnerable component encounters the parsing anomaly, leading directly to a denial of service state through application termination.\nAffected software versions include 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18. The post-exploitation impact is strictly limited to availability disruption, specifically crashing the parser process and potentially interrupting dependent services without granting remote code execution or unauthorized data access based on available indicators."
}