Menu

Star on GitHub · 3.2k

CVE-2011-2240

1.7 · LOW

Unspecified vulnerability in the Oracle Universal Installer component in Oracle Database Server 10.1.0.5 allows local users to affect confidentiality via unknown vectors.

Published Jul 20, 2011oracleEPSS 0.35%

Overview

CVE-2011-2240 is a low-severity vulnerability affecting oracle database_server. It was published on July 20, 2011 and has a CVSS 2.0 base score of 1.7 (LOW).

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

Technical description

Unspecified vulnerability in the Oracle Universal Installer component in Oracle Database Server 10.1.0.5 allows local users to affect confidentiality via unknown vectors.

Remediation

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

Frequently asked questions

What is CVE-2011-2240?

CVE-2011-2240 is a low-severity vulnerability affecting oracle database_server. It was published on July 20, 2011 and has a CVSS 2.0 base score of 1.7 (LOW).

How severe is CVE-2011-2240?

This vulnerability has a CVSS 2.0 base score of 1.7, 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-2011-2240?

Check the references section for vendor advisories and patches from oracle. Update database_server 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-2011-2240?

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

View all