Release-number disclosure through public calendar exports
Published Jun 13, 2022 · Updated Sep 17, 2024
Information disclosure in OTRS and OTRSCalendarResourcePlanning allows remote authenticated users to obtain the release number from a shared ICS file. The calendar export path writes the OTRS release number into the generated ICS file when Secure::DisableBanner is disabled. An agent must disable the banner setting and share a calendar through a public URL; the resulting disclosure is limited to software-version information.
Summary
What happened
Information disclosure in OTRS and OTRSCalendarResourcePlanning allows remote authenticated users to obtain the release number from a shared ICS file. The calendar export path writes the OTRS release number into the generated ICS file when Secure::DisableBanner is disabled. An agent must disable the banner setting and share a calendar through a public URL; the resulting disclosure is limited to software-version information.
The record
- CVE
- CVE-2022-32739
- Published
- Jun 13, 2022
- Updated
- Sep 17, 2024
- Vendor
- OTRS AG
- Product
- OTRS
- Classifications
- CWE-200, T1592.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=7.0.x <=7.0.34
- Affected versionversion=8.0.x <=8.0.22
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