Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2023-45718

3.9 · LOW

Sametime is impacted by a failure to invalidate sessions.

Published Feb 9, 2024CWE-384EPSS 0.35%

Overview

CVE-2023-45718 is a low-severity vulnerability. It was published on February 9, 2024 and has a CVSS 3.1 base score of 3.9 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

Sametime is impacted by a failure to invalidate sessions. The application is setting sensitive cookie values in a persistent manner in Sametime Web clients. When this happens, cookie values can remain valid even after a user has closed out their session.  

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refsupport.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0109082Refsupport.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0109082

How CyberStrike helps

Frequently asked questions

What is CVE-2023-45718?

CVE-2023-45718 is a low-severity vulnerability. It was published on February 9, 2024 and has a CVSS 3.1 base score of 3.9 (LOW).

How severe is CVE-2023-45718?

This vulnerability has a CVSS 3.1 base score of 3.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-45718?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-45718?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-45718 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2023

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999