CVE-2011-1938

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

Stack-based buffer overflow in the socket_connect function in ext/sockets/sockets.c in PHP 5.3.3 through 5.3.6 might allow context-dependent attackers to execute arbitrary code via a long pathname for a UNIX socket.

Statement

Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4 and 5. It has been addressed in Red Hat Enterprise Linux 5 (php53) and 6 (php).

Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4 and 5. It has been addressed in Red Hat Enterprise Linux 5 (php53) and 6 (php).

Additional information

  • Bugzilla 709067: php: stack-based buffer overflow in socket_connect()
  • CWE-121: Stack-based Buffer Overflow
  • FAQ: Frequently asked questions about CVE-2011-1938

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

2.6

7.5

Attack Vector

Network

Network

Access Complexity

High

Low

Authentication

None

None

Confidentiality Impact

None

Partial

Integrity Impact

None

Partial

Availability Impact

Partial

Partial

CVSS v2 Vector

Red Hat: AV:N/AC:H/Au:N/C:N/I:N/A:P

NVD: AV:N/AC:L/Au:N/C:P/I:P/A:P

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.