high
7.2
CWE
264
Advisory Published
CVE Published
Updated

CVE-2010-2199

First published: Tue Jun 01 2010(Updated: )

Common Vulnerabilities and Exposures assigned an identifier <a href="https://access.redhat.com/security/cve/CVE-2010-2199">CVE-2010-2199</a> to the following vulnerability: Name: <a href="https://access.redhat.com/security/cve/CVE-2010-2199">CVE-2010-2199</a> URL: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2199">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2199</a> Assigned: 20100608 Reference: CONFIRM: <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED UPSTREAM - CVE-2005-4889 rpm: Updates leave hardlinked copies untouched." href="show_bug.cgi?id=125517">https://bugzilla.redhat.com/show_bug.cgi?id=125517</a> lib/fsm.c in RPM 4.8.0 and earlier does not properly reset the metadata of an executable file during replacement of the file in an RPM package upgrade or deletion of the file in an RPM package removal, which might allow local users to bypass intended access restrictions by creating a hard link to a vulnerable file that has a POSIX ACL, a related issue to <a href="https://access.redhat.com/security/cve/CVE-2010-2059">CVE-2010-2059</a>. See <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2010-2059 rpm: fails to drop SUID/SGID bits on package upgrade" href="show_bug.cgi?id=598775">bug #598775</a> for an initial description and comments of this issue. Because different CVE names were assigned for different, yet related, issues, a separate bug has been filed for this particular issue.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
RPM Package Manager=2.3.5
RPM Package Manager=4.4.2.1
RPM Package Manager=1.4.3
RPM Package Manager=3.0.1
RPM Package Manager=4.1
RPM Package Manager=2.2.3.11
RPM Package Manager=2.4.4
RPM Package Manager=2.3.8
RPM Package Manager=2.0.6
RPM Package Manager=1.4.4
RPM Package Manager=4.4.2
RPM Package Manager=1.4.2\/a
RPM Package Manager=2.4.1
RPM Package Manager=2.4.9
RPM Package Manager=2.6.7
RPM Package Manager=2..4.10
RPM Package Manager=1.4
RPM Package Manager=2.0.10
RPM Package Manager=2.4.5
RPM Package Manager=4.0.1
RPM Package Manager=2.2.11
RPM Package Manager=4.0.4
RPM Package Manager=2.2.1
RPM Package Manager=2.0.1
RPM Package Manager=1.4.2
RPM Package Manager=3.0.3
RPM Package Manager=2.0.7
RPM Package Manager=4.0.2
RPM Package Manager=2.2.8
RPM Package Manager=3.0.2
RPM Package Manager=1.2
RPM Package Manager=4.0.
RPM Package Manager=2.1.1
RPM Package Manager=4.3.3
RPM Package Manager=2.5.5
RPM Package Manager=2.0.8
RPM Package Manager=2.3
RPM Package Manager=4.4.2.2
RPM Package Manager=2.4.8
RPM Package Manager=3.0.4
RPM Package Manager=2.5.6
RPM Package Manager=2.0
RPM Package Manager=2.0.2
RPM Package Manager=2.3.2
RPM Package Manager=2.4.3
RPM Package Manager=2.4.2
RPM Package Manager=1.4.5
RPM Package Manager=2.0.11
RPM Package Manager=3.0.5
RPM Package Manager=1.3
RPM Package Manager=2.2.3
RPM Package Manager=2.2
RPM Package Manager=2.1.2
RPM Package Manager=2.3.9
RPM Package Manager=2.2.4
RPM Package Manager=2.2.9
RPM Package Manager=2.5.3
RPM Package Manager=2.2.6
RPM Package Manager=2.3.6
RPM Package Manager=2.5
RPM Package Manager=2.2.3.10
RPM Package Manager=2.0.5
RPM Package Manager=4.4.2.3
RPM Package Manager=2.4.12
RPM Package Manager=2.5.4
RPM Package Manager=1.4.7
RPM Package Manager=3.0
RPM Package Manager=1.4.6
RPM Package Manager=2.5.2
RPM Package Manager=2.4.11
RPM Package Manager=2.0.9
RPM Package Manager=2.1
RPM Package Manager=2.2.10
RPM Package Manager=2.3.3
RPM Package Manager=2.3.7
RPM Package Manager=2.3.4
RPM Package Manager=2.0.4
RPM Package Manager=1.3.1
RPM Package Manager=3.0.6
RPM Package Manager=2.0.3
RPM Package Manager=2.3.1
RPM Package Manager=4.0.3
RPM Package Manager=2.4.6
RPM Package Manager=2.5.1
RPM Package Manager=2.2.5
RPM Package Manager=2.2.2
RPM Package Manager=2.2.7
RPM Package Manager=4.6.0
RPM Package Manager<=4.8.0
RPM Package Manager=4.7.2
RPM Package Manager=4.7.0
RPM Package Manager=4.6.1
RPM Package Manager=4.7.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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2010-2199?

    CVE-2010-2199 is rated as a high-severity vulnerability that can lead to buffer overflow exploits.

  • How do I fix CVE-2010-2199?

    To fix CVE-2010-2199, you need to upgrade RPM Package Manager to the latest version that has addressed the vulnerability.

  • Which versions of RPM Package Manager are affected by CVE-2010-2199?

    CVE-2010-2199 affects multiple versions of RPM Package Manager, including 1.2, 2.0.1, 3.0.1, and all the way up to 4.4.2.3.

  • What is the impact of CVE-2010-2199?

    The impact of CVE-2010-2199 can result in remote code execution and take control of affected systems.

  • Is there a workaround for CVE-2010-2199?

    While upgrading is the recommended fix, temporarily limiting RPM access may serve as a workaround until a patch is applied.

Company

Resources

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