Configuration disclosure via brute-forceable BOF encryption
Published Oct 17, 2024 · Updated Nov 5, 2024
Inadequate encryption in Nokia SR OS before Release 24 allows local users with an encrypted bof.cfg file to read BOF configuration content. The bof.cfg encryption mechanism protects the boot options file with cryptography that Nokia identifies as susceptible to brute-force recovery, but Nokia has not disclosed the defective construction. Exploitation requires possession of encrypted bof.cfg; decryption exposes only stored BOF configuration content, with no reported modification or service interruption.
Summary
What happened
Inadequate encryption in Nokia SR OS before Release 24 allows local users with an encrypted bof.cfg file to read BOF configuration content. The bof.cfg encryption mechanism protects the boot options file with cryptography that Nokia identifies as susceptible to brute-force recovery, but Nokia has not disclosed the defective construction. Exploitation requires possession of encrypted bof.cfg; decryption exposes only stored BOF configuration content, with no reported modification or service interruption.
The record
- CVE
- CVE-2023-6728
- Published
- Oct 17, 2024
- Updated
- Nov 5, 2024
- Vendor
- Nokia
- Product
- Service Router Operating System (SR OS)
- Classifications
- CWE-326, T1140
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All supported releases prior to Release 24
What conditions does exploitation require?
What is affected?
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