CVE-2013-1762

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

stunnel 4.21 through 4.54, when CONNECT protocol negotiation and NTLM authentication are enabled, does not correctly perform integer conversion, which allows remote proxy servers to execute arbitrary code via a crafted request that triggers a buffer overflow.

Statement

This issue did not affect the version of the stunnel package as shipped with Red Hat Enterprise Linux 5.

This issue did not affect the version of the stunnel package as shipped with Red Hat Enterprise Linux 5.

Additional information

  • Bugzilla 917839: Stunnel: buffer overflow vulnerability due to incorrect integer conversion in the NTLM authentication of the CONNECT protocol negotiation
  • FAQ: Frequently asked questions about CVE-2013-1762

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

5.1

6.6

Attack Vector

Network

Network

Access Complexity

High

High

Authentication

None

None

Confidentiality Impact

Partial

Partial

Integrity Impact

Partial

Partial

Availability Impact

Partial

Complete

CVSS v2 Vector

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

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

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?

My product is listed as "Out of Support Scope". What does this mean?

Want to get errata notifications? Sign up here.