# What is CVE-2010-5171? > CVE-2010-5171 is a medium-severity flaw (CVSS 6.2) in Outpost Security Suite from Agnitum, published on 25 August 2012. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.3%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2010-5171 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 18 out of 100 (Info); action: Track. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 6.2 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.3% (latest exploit-likelihood forecast) - **Published:** 25 August 2012 - **Record last updated:** 16 June 2026 - **Main product:** Outpost Security Suite from Agnitum - **Affected products:** 1 ## What is CVE-2010-5171? In plain terms An attacker has to be already on the device without logging in. If it works, the attacker can read data, change data and take it offline. ### The official description Race condition in Outpost Security Suite Pro 6.7.3.3063.452.0726 and 7.0.3330.505.1221 BETA on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack. NOTE: this issue is disputed by some third parties because it is a flaw in a protection mechanism for situations where a crafted program has already begun to execute ### What kind of flaw is it? - CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') ### How an attack on it works - Where an attacker can be: Already on the device - How hard it is to pull off: Hard: conditions must line up - Login needed first: No login needed - What an attacker gets: Can read data, change data and take it offline Severity vector: `AV:L/AC:H/Au:N/C:C/I:C/A:C` ## Is CVE-2010-5171 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.3%, 0.3%, 0.3%, 0.3%, 0.3%, 0.3%, 0.3%. ### Timeline - 25 August 2012: Published - 16 June 2026: Record last updated ### How Precursor Intelligence ranks it CVE-2010-5171 scores **18 out of 100 (Info)**, with the action "Track". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2010-5171? The published record lists 1 product. - [Outpost Security Suite](https://www.precursorintelligence.com/product/agnitum/outpost_security_suite) by [Agnitum](https://www.precursorintelligence.com/vendors/agnitum) (Application): 6.7.3.3063.452.0726, 7.0.3330.505.1221-beta ## How do I fix CVE-2010-5171? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [archives.neohapsis.com](http://archives.neohapsis.com/archives/bugtraq/2010-05/0026.html) - [archives.neohapsis.com](http://archives.neohapsis.com/archives/fulldisclosure/2010-05/0066.html) - [countermeasures.trendmicro.eu](http://countermeasures.trendmicro.eu/you-just-cant-trust-a-drunk/) - [matousec.com](http://matousec.com/info/advisories/khobe-8.0-earthquake-for-windows-desktop-security-software.php) - [matousec.com](http://matousec.com/info/articles/khobe-8.0-earthquake-for-windows-desktop-security-software.php) - [f-secure.com](http://www.f-secure.com/weblog/archives/00001949.html) - [osvdb.org](http://www.osvdb.org/67660) - [securityfocus.com](http://www.securityfocus.com/bid/39924) - [theregister.co.uk](http://www.theregister.co.uk/2010/05/07/argument_switch_av_bypass/) ## Questions ### What is CVE-2010-5171? CVE-2010-5171 is a medium-severity flaw in Outpost Security Suite from Agnitum, published on 25 August 2012. An attacker has to be already on the device without logging in. If it works, the attacker can read data, change data and take it offline. ### How serious is CVE-2010-5171? It scores 6.2 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2010-5171 is 18 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2010-5171 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2010-5171 affect? For Outpost Security Suite from Agnitum: 6.7.3.3063.452.0726, 7.0.3330.505.1221-beta. ### How do I fix CVE-2010-5171? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2010-5171 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact