Description

3gpp phone log 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": "4.7",
  "pubDate": "2026-08-19T23:16:20.727Z",
  "pubdate": "2026-08-19T23:16:20.727Z",
  "executiveSummary": "A denial of service vulnerability exists within the 3GPP phone log file parser affecting versions 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18. The flaw allows an unauthenticated attacker to cause application crashes or complete service disruption by supplying a maliciously crafted 3GPP log file for parsing. The primary impact is the loss of availability of the log processing functionality and potentially the host application processing the logs. Exploitation of this vulnerability requires an attacker to successfully induce the target system or user to parse a specially formatted input file, leading to abnormal termination of the parsing engine. The risk implication centers on operational disruption in environments that automatically process or analyze telecommunications log data. No elevated privileges are explicitly required beyond the ability to supply the malformed input to the vulnerable parser component.",
  "technicalDetails": "The vulnerability resides in the 3GPP phone log file parser component, specifically impacting software versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. The root cause is improper handling of malformed or maliciously structured 3GPP log formats, which triggers an unhandled exception, null pointer dereference, buffer over-read, or logic error during the file parsing lifecycle. When the vulnerable component attempts to read and interpret the engineered file, the structural anomalies within the input violate parser assumptions regarding record lengths, header fields, or encoding parameters.\nThe attack flow begins when an adversary generates or supplies a maliciously crafted 3GPP phone log file. The attack vector is local or remote depending on how the parser is invoked, such as via an automated log ingestion pipeline, an application programming interface accepting file uploads, or manual user intervention. Once the vulnerable parsing function initiates execution against the malformed input, the internal state machine or memory management routine encounters the unexpected data layout. Because input validation routines fail to properly sanitize or bound-check the file contents, the execution flow deviates into an unsafe code path.\nThis behavior results in a fatal application crash, manifesting as a denial of service condition for the log parsing subsystem. Network exposure and authentication requirements depend entirely on the wrapper application implementing the parser; however, the parsing engine itself operates without inherent access controls once fed the payload. Post-exploitation impact is strictly limited to availability disruption, as the crash terminates the process and prevents further log analysis until manual or automated service recovery occurs. There is no evidence of arbitrary code execution or privilege escalation associated directly with this specific parsing crash vector based on the provided vulnerability description."
}