Menu

Star on GitHub · 3.2k

CVE-2011-3268

10.0 · HIGH

Buffer overflow in the crypt function in PHP before 5.3.7 allows context-dependent attackers to have an unspecified impact via a long salt argument, a different vulnerability than CVE-2011-2483.

Published Aug 25, 2011phpCWE-119EPSS 5.72%

Overview

CVE-2011-3268 is a high-severity vulnerability affecting php php. It was published on August 25, 2011 and has a CVSS 2.0 base score of 10.0 (HIGH).

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

Technical description

Buffer overflow in the crypt function in PHP before 5.3.7 allows context-dependent attackers to have an unspecified impact via a long salt argument, a different vulnerability than CVE-2011-2483.

Remediation

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

Frequently asked questions

What is CVE-2011-3268?

CVE-2011-3268 is a high-severity vulnerability affecting php php. It was published on August 25, 2011 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2011-3268?

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

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

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

View all