Syslog message injection via trusted serial numbers
Published Oct 10, 2023 · Updated Sep 18, 2024
Insufficient authenticity verification in Fortinet FortiAnalyzer products allows remote attackers to inject forged syslog messages. The syslog receiver accepts messages carrying a known authorized-device serial number without an additional authentication layer. Knowledge of a registered serial number is required, and successful exploitation can falsify logged events without reading data or interrupting service.
Summary
What happened
Insufficient authenticity verification in Fortinet FortiAnalyzer products allows remote attackers to inject forged syslog messages. The syslog receiver accepts messages carrying a known authorized-device serial number without an additional authentication layer. Knowledge of a registered serial number is required, and successful exploitation can falsify logged events without reading data or interrupting service.
The record
- CVE
- CVE-2023-42782
- Published
- Oct 10, 2023
- Updated
- Sep 18, 2024
- Vendor
- Fortinet
- Product
- FortiManager
- Classifications
- CWE-345, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2023CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=6.2
- Affected versionversion=6.4
- Affected versionversion=7.0.0 <=7.0.9
- Affected versionversion=7.2.0 <=7.2.3
- Affected versionversion=7.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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