Security weakening via improper resource expiration
Published Oct 25, 2023 · Updated Sep 10, 2024
Insufficient session expiration in IBM WebSphere Application Server Liberty 23.0.0.9 through 23.0.0.10 allows local users to weaken security. IBM attributes the flaw to improper resource expiration handling in the appSecurity feature set but keeps the implementation details confidential. The condition requires appSecurity-1.0 through appSecurity-5.0 to be enabled; IBM has not disclosed which resources remain usable or the concrete operations an attacker gains.
Summary
What happened
Insufficient session expiration in IBM WebSphere Application Server Liberty 23.0.0.9 through 23.0.0.10 allows local users to weaken security. IBM attributes the flaw to improper resource expiration handling in the appSecurity feature set but keeps the implementation details confidential. The condition requires appSecurity-1.0 through appSecurity-5.0 to be enabled; IBM has not disclosed which resources remain usable or the concrete operations an attacker gains.
The record
- CVE
- CVE-2023-46158
- Published
- Oct 25, 2023
- Updated
- Sep 10, 2024
- Vendor
- IBM
- Product
- IBM WebSphere Application Server Liberty
- Classifications
- CWE-613
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Sep 10, 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=23.0.0.9, 23.0.0.10
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