CVE-2012-5195

Public on

Last Modified: UTC

ModerateModerate ImpactWhat does this mean?

Insights vulnerability analysis

View exposed systems

Description

The CVE Program describes this issue as:

Heap-based buffer overflow in the Perl_repeatcpy function in util.c in Perl 5.12.x before 5.12.5, 5.14.x before 5.14.3, and 5.15.x before 15.15.5 allows context-dependent attackers to cause a denial of service (memory consumption and crash) or possibly execute arbitrary code via the 'x' string repeat operator.

Additional information

  • Bugzilla 862413: perl: heap buffer overrun flaw may lead to arbitrary code execution
  • FAQ: Frequently asked questions about CVE-2012-5195

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

7.5

Attack Vector

Network

Network

Access Complexity

High

Low

Authentication

None

None

Confidentiality Impact

Partial

Partial

Integrity Impact

Partial

Partial

Availability Impact

Partial

Partial

CVSS v2 Vector

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

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

Acknowledgements

Red Hat would like to thank Perl project for reporting this issue. Upstream acknowledges Tim Brown as the original reporter.

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.