VulnerabilityPublished 29 Jan 2024Updated 29 May 2025

CVE-2024-23791: OTRS · Sensitive Data in Logs

Affects OTRSSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium · fixed in 2024.0.0 : update OTRS when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2024.0.0, 8.1.0, 7.1.0

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade OTRS to 2024.0.0, 8.1.0 or 7.1.0.

Affected software

Product	Affected	Fixed in
OTRS AG OTRS	Affected >=7.0.0 <7.1.0 >=8.0.0 <8.1.0 >=2023.0.0 <2024.0.0	Fixed in 7.1.0 8.1.0 2024.0.0

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately review and restrict access to OTRS log files to only trusted administrators and systems with a strict need-to-know basis. 2) Monitor and audit access to logs to detect any unauthorized or suspicious activity. 3) Disable or limit debug logging during Elasticsearch index building or in production environments to prevent sensitive data from being logged. 5) Encrypt log files at rest and in transit to reduce the risk of data exposure if logs are accessed improperly. 6) Conduct internal security awareness training to ensure privileged users understand the sensitivity of log data and the importance of secure handling. 7) Implement strong access controls and multi-factor authentication for accounts with high privileges in OTRS to reduce the risk of credential compromise. 8) Regularly review and update incident response plans to include scenarios involving sensitive data leakage through logs.

Description

Insertion of debug information into log file during building the elastic search index allows reading of sensitive information from articles.This issue affects OTRS: from 7.0.X through 7.0.48, from 8.0.X through 8.0.37, from 2023.X through 2023.1.1.

Impact

For European organizations, the impact of CVE-2024-23791 can be considerable, especially for those relying on OTRS for managing sensitive customer support tickets, internal communications, or incident tracking. The exposure of sensitive information in logs can lead to unauthorized disclosure of confidential data, potentially violating GDPR requirements on data protection and privacy. This could result in regulatory fines, reputational damage, and loss of customer trust. Additionally, attackers or malicious insiders with access to these logs could leverage the leaked information to escalate privileges, conduct social engineering, or launch targeted attacks. Since the vulnerability requires high privileges to exploit, the risk is primarily from insiders or attackers who have already compromised accounts with elevated access. However, given that OTRS is often deployed in critical IT service environments, any data leakage could disrupt operational security and compliance postures. The medium severity rating suggests that while the vulnerability is not immediately critical, it should be addressed promptly to prevent potential data breaches and compliance violations.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

otrs.com/release-notes/otrs-security-advisory-2024-02/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 23:59 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats