Audit-log pollution via missing scope checks
Published May 4, 2022 · Updated Aug 3, 2024
Excessive audit logging in Secomea GateManager before 9.7 allows remote authenticated users to add unrelated text entries to the audit log. The audit-log write path accepts user-supplied text without enforcing that the entry relates to an action or object within the user's authorized scope. Any logged-in account can pollute the security record with misleading entries, but the published assessment reports no confidentiality or availability impact.
Summary
What happened
Excessive audit logging in Secomea GateManager before 9.7 allows remote authenticated users to add unrelated text entries to the audit log. The audit-log write path accepts user-supplied text without enforcing that the entry relates to an action or object within the user's authorized scope. Any logged-in account can pollute the security record with misleading entries, but the published assessment reports no confidentiality or availability impact.
The record
- CVE
- CVE-2022-25779
- Published
- May 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Secomea
- Product
- GateManager
- Classifications
- CWE-779, CWE-400
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <9.7
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