CVE-2010-5170
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRace condition in Online Solutions Security Suite 1.5.14905.0 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA race condition in Online Solutions Security Suite 1.5.14905.0 on Windows XP allows local attackers to bypass kernel-mode hook handlers by manipulating user-space memory during hook-handler execution. This 'argument-switch' or 'KHOBE' attack enables execution of code that would normally be blocked by handlers but not by signature-based detection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.5.14905.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:H/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify if Online Solutions Security Suite is installedCheck Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Online Solutions Security Suite' or look for the product in Add/Remove ProgramsAffected if The product is listed as installed on the system
-
Confirm the installed version is 1.5.14905.0Retrieve the DisplayVersion value from the product's registry key found in the previous stepAffected if The version displayed is exactly 1.5.14905.0
-
Locate the executable to verify product presenceSearch for files named 'osss.exe', 'Online Solutions Security Suite.exe', or similar in Program Files directories (e.g., C:\Program Files\Online Solutions\)Affected if The executable exists and its version property shows 1.5.14905.0
-
Verify the product is actively running or set to runCheck Windows Registry Run keys (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) for entries referencing Online Solutions security components, or view running processes for osssec.exe, osss.exe, or similarAffected if The security suite is running or configured to start with Windows
The system is affected if Online Solutions Security Suite version 1.5.14905.0 is installed and running on the system, as this specific version contains the race condition vulnerability that allows local attackers to bypass kernel-mode hook handlers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThis vulnerability requires vendor patches from Online Solutions Security Suite. Organizations should evaluate whether this legacy security product is still supported and consider upgrading or replacing it with actively maintained endpoint protection. Consider compensating controls such as application whitelisting and restricting local user privileges.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-5170 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data