AI Engine: Insertion of Sensitive Information into Log File
CVE-2024-6451 is a high-severity insertion of sensitive information into log file vulnerability in AI Engine, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 2.5.1 as the first without the flaw, so updating AI Engine to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update AI Engine to 2.5.1 or a later version.
- Update ai_engine to 2.5.1 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AI Engine | AI Engine | before 2.5.1 | 2.5.1 |
| Ai Engine Project | ai_engine | before 2.5.1 | 2.5.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
AI Engine < 2.4.3 is susceptible to remote-code-execution (RCE) via Log Poisoning. The AI Engine WordPress plugin before 2.5.1 fails to validate the file extension of "logs_path", allowing Administrators to change log filetypes from .log to .php.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- wpscan.com/vulnerability/fc06d413-a227-470c-a5b7-cdab57aeab34/Exploit, Third Party Advisory
Other vulnerabilities in AI Engine
- 7.7 High severity
- 7.2 High severity
- 7.2 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.3 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.