Menu

Star on GitHub · 3.2k

CVE-2008-4689

7.5 · HIGH

Mantis before 1.1.3 does not unset the session cookie during logout, which makes it easier for remote attackers to hijack sessions.

Published Oct 22, 2008mantisCWE-287EPSS 2.49%

Overview

CVE-2008-4689 is a high-severity vulnerability affecting mantis mantis. It was published on October 22, 2008 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Mantis before 1.1.3 does not unset the session cookie during logout, which makes it easier for remote attackers to hijack sessions.

Remediation

Check the references section for vendor advisories and patches from mantis. Update mantis to the latest patched version. 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.

Affected products

VendorProductVersionsStatus
mantismantis0Affected

Frequently asked questions

What is CVE-2008-4689?

CVE-2008-4689 is a high-severity vulnerability affecting mantis mantis. It was published on October 22, 2008 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2008-4689?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2008-4689?

Check the references section for vendor advisories and patches from mantis. Update mantis to the latest patched version. 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-2008-4689?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2008-4689 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 HIGH CVEs from 2008

View all