CWE
20
Advisory Published
CVE Published
Updated

CVE-2012-0061: Input Validation

First published: Wed 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: <a href="http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=472e569562d4c90d7a298080e0052856aa7fa86b">http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=472e569562d4c90d7a298080e0052856aa7fa86b</a> <a href="http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=858a328cd0f7d4bcd8500c78faaf00e4f8033df6">http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=858a328cd0f7d4bcd8500c78faaf00e4f8033df6</a>

Credit: secalert@redhat.com

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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • 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.

  • How do I fix CVE-2012-0061?

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

  • 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.

  • 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.

  • 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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203