Menu

Star on GitHub · 3.2k

CVE-2018-1626

3.1 · LOW

IBM Security Privileged Identity Manager Virtual Appliance 2.2.1 does not renew a session variable after a successful authentication which could lead to session fixation/hijacking vulnerability.

Published Apr 2, 2019CWE-384EPSS 1.14%

Overview

CVE-2018-1626 is a low-severity vulnerability. It was published on April 2, 2019 and has a CVSS 3.0 base score of 3.1 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

IBM Security Privileged Identity Manager Virtual Appliance 2.2.1 does not renew a session variable after a successful authentication which could lead to session fixation/hijacking vulnerability. This could force a user to utilize a cookie that may be known to an attacker. IBM X-Force ID: 144411.

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.

Frequently asked questions

What is CVE-2018-1626?

CVE-2018-1626 is a low-severity vulnerability. It was published on April 2, 2019 and has a CVSS 3.0 base score of 3.1 (LOW).

How severe is CVE-2018-1626?

This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2018-1626?

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-2018-1626?

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

View all