Database access via hard-coded service credentials
Published Sep 13, 2023 · Updated Sep 24, 2024
Hard-coded credentials in Fortinet FortiTester 2.3.0 through 7.2.3 allow local users with device shell access to authenticate to its database. The appliance stores a fixed credential for the database service, so shell commands can reuse that embedded secret instead of supplying a deployment-specific credential. Exploitation requires prior shell access to the device; successful use lets that shell user operate the database under the embedded account's permissions.
Summary
What happened
Hard-coded credentials in Fortinet FortiTester 2.3.0 through 7.2.3 allow local users with device shell access to authenticate to its database. The appliance stores a fixed credential for the database service, so shell commands can reuse that embedded secret instead of supplying a deployment-specific credential. Exploitation requires prior shell access to the device; successful use lets that shell user operate the database under the embedded account's permissions.
The record
- CVE
- CVE-2023-40717
- Published
- Sep 13, 2023
- Updated
- Sep 24, 2024
- Vendor
- Fortinet
- Product
- FortiTester
- Classifications
- CWE-798, T1078
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=2.3.0
- Affected versionversion=2.4.0 <=2.4.1
- Affected versionversion=2.5.0
- Affected versionversion=2.6.0
- Affected versionversion=2.7.0
- Affected versionversion=2.8.0
- Affected versionversion=2.9.0
- Affected versionversion=3.0.0
- Affected versionversion=3.1.0
- Affected versionversion=3.2.0
- Affected versionversion=3.3.0 <=3.3.1
- Affected versionversion=3.4.0
- Affected versionversion=3.5.0 <=3.5.1
- Affected versionversion=3.6.0
- Affected versionversion=3.7.0 <=3.7.1
- Affected versionversion=3.8.0
- Affected versionversion=3.9.0 <=3.9.2
- Affected versionversion=4.0.0
- Affected versionversion=4.1.0 <=4.1.1
- Affected versionversion=4.2.0 <=4.2.1
- Affected versionversion=7.0.0
- Affected versionversion=7.1.0 <=7.1.1
- Affected versionversion=7.2.0 <=7.2.3
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.
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