CVE-2012-0061: Input Validation

Published Feb 29, 2012
·
Updated

It was discovered that RPM did not properly validate region size in headerLoad() when loading header from an RPM file, allowing region size to exceed containing header size. A malformed or malicious RPM file could cause RPM to crash and possibly execute arbitrary code before file signature was properly verified.

Upstream commits: http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=472e569562d4c90d7a298080e0052856aa7fa86b http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=858a328cd0f7d4bcd8500c78faaf00e4f8033df6

Other sources

The headerLoad function in lib/header.c in RPM before 4.9.1.3 does not properly validate region tags, which allows user-assisted remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large region size in a package header.

Affected Software

106 affected componentsFixes available
redhat/rpm<4.9.1.3
4.9.1.3
RPM RPM<=4.9.1.2
RPM RPM=1.2
RPM RPM=1.3
RPM RPM=1.3.1
RPM RPM=1.4
RPM RPM=1.4.1
RPM RPM=1.4.2
RPM RPM=1.4.2\/a
RPM RPM=1.4.3
RPM RPM=1.4.4
RPM RPM=1.4.5
RPM RPM=1.4.6
RPM RPM=1.4.7
RPM RPM=2.0
RPM RPM=2.0.1
RPM RPM=2.0.2
RPM RPM=2.0.3
RPM RPM=2.0.4
RPM RPM=2.0.5
RPM RPM=2.0.6
RPM RPM=2.0.7
RPM RPM=2.0.8
RPM RPM=2.0.9
RPM RPM=2.0.10
RPM RPM=2.0.11
RPM RPM=2.1
RPM RPM=2.1.1
RPM RPM=2.1.2
RPM RPM=2.2
RPM RPM=2.2.1
RPM RPM=2.2.2
RPM RPM=2.2.3
RPM RPM=2.2.3.10
RPM RPM=2.2.3.11
RPM RPM=2.2.4
RPM RPM=2.2.5
RPM RPM=2.2.6
RPM RPM=2.2.7
RPM RPM=2.2.8
RPM RPM=2.2.9
RPM RPM=2.2.10
RPM RPM=2.2.11
RPM RPM=2.3
RPM RPM=2.3.1
RPM RPM=2.3.2
RPM RPM=2.3.3
RPM RPM=2.3.4
RPM RPM=2.3.5
RPM RPM=2.3.6
RPM RPM=2.3.7
RPM RPM=2.3.8
RPM RPM=2.3.9
RPM RPM=2.4.1
RPM RPM=2.4.2
RPM RPM=2.4.3
RPM RPM=2.4.4
RPM RPM=2.4.5
RPM RPM=2.4.6
RPM RPM=2.4.8
RPM RPM=2.4.9
RPM RPM=2.4.11
RPM RPM=2.4.12
RPM RPM=2.5
RPM RPM=2.5.1
RPM RPM=2.5.2
RPM RPM=2.5.3
RPM RPM=2.5.4
RPM RPM=2.5.5
RPM RPM=2.5.6
RPM RPM=2.6.7
RPM RPM=3.0
RPM RPM=3.0.1
RPM RPM=3.0.2
RPM RPM=3.0.3
RPM RPM=3.0.4
RPM RPM=3.0.5
RPM RPM=3.0.6
RPM RPM=4.0.
RPM RPM=4.0.1
RPM RPM=4.0.2
RPM RPM=4.0.3
RPM RPM=4.0.4
RPM RPM=4.1
RPM RPM=4.3.3
RPM RPM=4.4.2.1
RPM RPM=4.4.2.2
RPM RPM=4.4.2.3
RPM RPM=4.5.90
RPM RPM=4.6.0
RPM RPM=4.6.0-rc1
RPM RPM=4.6.0-rc2
RPM RPM=4.6.0-rc3
RPM RPM=4.6.0-rc4
RPM RPM=4.6.1
RPM RPM=4.7.0
RPM RPM=4.7.1
RPM RPM=4.7.2
RPM RPM=4.8.0
RPM RPM=4.8.1
RPM RPM=4.9.0
RPM RPM=4.9.0-alpha
RPM RPM=4.9.0-beta1
RPM RPM=4.9.0-rc1
RPM RPM=4.9.1
RPM RPM=4.9.1.1

Event History

Feb 29, 2012
Data Sourced
via Red Hat·10:31 AM
DescriptionSeverityAffected Software
Jun 4, 2012
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-0061?

CVE-2012-0061 is classified with medium severity due to the potential for a crash or arbitrary code execution through a malformed RPM file.

2

How do I fix CVE-2012-0061?

To fix CVE-2012-0061, upgrade the RPM package to version 4.9.1.3 or later.

3

Which software is affected by CVE-2012-0061?

CVE-2012-0061 affects various versions of the RPM package manager, specifically versions up to 4.9.1.2.

4

What are the potential impacts of CVE-2012-0061?

The potential impacts of CVE-2012-0061 include application crashes and possible execution of arbitrary code.

5

Is CVE-2012-0061 a remote or local vulnerability?

CVE-2012-0061 is considered a local vulnerability as it requires a user to execute a malicious RPM file.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203