Anti VirusApplication · Sophos

CVE-2008-1737

MEDIUM · 6.9 CVSS v2.0 Published 2008-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Sophos Anti-Virus 7.0.5, and other 7.x versions, when Runtime Behavioural Analysis is enabled, allows local users to cause a denial of service (reboot with the product disabled) and possibly gain privileges via a zero value in a certain length field in the ObjectAttributes argument to the NtCreateKey hooked System Service Descriptor Table (SSDT) function.

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 · high confidence

Sophos Anti-Virus 7.x versions with Runtime Behavioural Analysis enabled contain a local privilege escalation and denial of service vulnerability. The hooked NtCreateKey SSDT function improperly handles a zero value in a length field within the ObjectAttributes argument, allowing local users to cause the product to disable and potentially gain elevated privileges.

MitigationDisable the Runtime Behavioural Analysis feature in Sophos Anti-Virus 7.x, or upgrade to a version that addresses this vulnerability. If upgrading is not immediately feasible, disabling the behavioural analysis provides a compensating control.

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
Anti VirusApplication
Affected:= 7.0.5

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sophos Anti-Virus is installed
    Check for Sophos Anti-Virus installation by reviewing installed programs in Control Panel or querying the Windows registry under HKLM\SOFTWARE\Sophos for the product installation
    Affected if Sophos Anti-Virus is not found on the system - the system is not affected by this CVE
  2. Confirm the installed version
    Locate the Sophos Anti-Virus version information in the program files directory (typically under Sophos\Sophos Anti-Virus) or via the Windows registry at HKLM\SOFTWARE\Sophos\Sophos Anti-Virus\Version
    Affected if The installed version is 7.0.5 - this version is specifically listed as affected; versions outside 7.x are not in scope for this CVE
  3. Determine if Runtime Behavioural Analysis is enabled
    Open the Sophos Anti-Virus console or configuration settings and locate the Runtime Behavioural Analysis feature status, or query the Windows registry under HKLM\SOFTWARE\Sophos\Sophos Anti-Virus\BehaviouralAnalysis for the enabled state
    Affected if Runtime Behavioural Analysis is turned ON or set to an enabled state - this feature must be active for the vulnerability to be exploitable
  4. Verify the SSDT hook is present
    Use a kernel debugging tool or a system utility capable of inspecting the System Service Descriptor Table to confirm that Sophos has hooked the NtCreateKey function; this hook is created when Runtime Behavioural Analysis is loaded
    Affected if The NtCreateKey SSDT hook from Sophos is present in the kernel - the vulnerable code path is active when the hook exists

A system is affected only if Sophos Anti-Virus version 7.0.5 is installed AND Runtime Behavioural Analysis feature is enabled, allowing the vulnerable NtCreateKey SSDT hook to be active in kernel mode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Runtime Behavioural Analysis feature in Sophos Anti-Virus 7.x, or upgrade to a version that addresses this vulnerability. If upgrading is not immediately feasible, disabling the behavioural analysis provides a compensating control.

Fix this in Anti Virus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-1737 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-1737 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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