CyberRota Analysis
AI-GeneratedThe AUSF component of free5GC versions prior to 1.4.5 is vulnerable due to improper cryptographic authentication comparisons, which can lead to potential timing attacks and expose sensitive authentication material through INFO-level logging. While the risk of a practical remote timing oracle is low due to environmental noise, the exposure of authentication data in logs poses a security concern. Organizations using affected versions of free5GC should prioritize upgrading to version 1.4.5 to mitigate these vulnerabilities.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
free5GC is an open-source implementation of the 5G core network. Prior to 1.4.5, the AUSF component performs cryptographic authentication comparisons in internal/sbi/processor/ue_authentication.go with ordinary equality helpers. Auth5gAkaComfirmRequestProcedure compares RES* and XRES* with strings.EqualFold and logs the expected XRES* value at INFO level before comparison. EapAuthComfirmRequestProcedure compares AT_MAC and XMAC with bytes.Equal and evaluates XRES == RES with ordinary string equality. These comparisons can return at mismatch-dependent times, although testing did not demonstrate a practical remote timing oracle because of HTTP/SBI timing noise. The INFO log exposes authentication material to operators, log collectors, sidecars, or processes able to read AUSF logs. This issue is fixed in version 1.4.5.