Menu

Star on GitHub · 3.2k

CVE-2010-1243

7.5 · HIGH

The IBM Web Interface for Content Management (aka WEBi) before 1.0.4 creates persistent cookies on client workstations, which has unspecified impact and attack vectors.

Published Apr 5, 2010ibmEPSS 1.20%

Overview

CVE-2010-1243 is a high-severity vulnerability affecting ibm webi. It was published on April 5, 2010 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

The IBM Web Interface for Content Management (aka WEBi) before 1.0.4 creates persistent cookies on client workstations, which has unspecified impact and attack vectors.

Remediation

Check the references section for vendor advisories and patches from ibm. Update webi 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
ibmwebi0Affected

Frequently asked questions

What is CVE-2010-1243?

CVE-2010-1243 is a high-severity vulnerability affecting ibm webi. It was published on April 5, 2010 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2010-1243?

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-2010-1243?

Check the references section for vendor advisories and patches from ibm. Update webi 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-2010-1243?

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

View all