dbcve.org
SizeroneApplication · Componentone

CVE-2008-4827

HIGH · 9.3 CVSS v2.0 Published 2009-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Multiple heap-based buffer overflows in the AddTab method in the (1) Tab and (2) CTab ActiveX controls in c1sizer.ocx and the (3) TabOne ActiveX control in sizerone.ocx in ComponentOne SizerOne 8.0.20081.140, as used in ComponentOne Studio for ActiveX 2008, TSC2 Help Desk 4.1.8, SAP GUI 6.40 Patch 29 and 7.10, and possibly other products, allow remote attackers to execute arbitrary code by adding many tabs, or adding tabs with long tab captions.

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

Heap-based buffer overflow in the AddTab method of ComponentOne SizerOne ActiveX controls (c1sizer.ocx and sizerone.ocx) allows remote code execution by supplying either excessive tab counts or overly long tab caption strings. The vulnerability affects multiple products embedding these controls including ComponentOne Studio, TSC2 Help Desk, and SAP GUI.

MitigationDisable or remove the affected ActiveX controls (c1sizer.ocx and sizerone.ocx) from vulnerable systems. If the controls are required, apply vendor patches from ComponentOne. Alternatively, set the 'Kill Bit' in the Windows registry to prevent the controls from loading in Internet Explorer.

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
SizeroneApplication
Affected:= 8.0.20081.140
Sap GuiApplication
Affected:= 6.40= 7.10
TaboneApplication
Affected:= 7.0.0.16
Tsc2 Help DeskApplication
Affected:= 4.18

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

AV:N/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. Locate the affected ActiveX control files
    Search the filesystem for c1sizer.ocx and sizerone.ocx using: `dir /s /b C:\c1sizer.ocx 2>nul` and `dir /s /b C:\sizerone.ocx 2>nul` or use Windows Search. Also check in application installation directories commonly used by ComponentOne products.
    Affected if Either c1sizer.ocx or sizerone.ocx is found on the system
  2. Identify the file version of the OCX control
    Right-click each found OCX file, select Properties, then view the Version tab. Alternatively, use PowerShell: `(Get-Item 'C:\path\to\c1sizer.ocx').VersionInfo.FileVersion`
    Affected if The version matches 8.0.20081.140 or falls within the affected product version ranges
  3. Check if the controls are registered in Windows
    Open Registry Editor and navigate to `HKLM\SOFTWARE\Classes\CLSID` and search for CLSIDs associated with C1Sizer.SizerOne or similar ComponentOne controls. Or run: `reg query HKLM\SOFTWARE\Classes\CLSID /s | findstr /i "c1sizer"`
    Affected if The controls are registered in the Windows registry and can be instantiated by Internet Explorer or other applications
  4. Verify presence of affected SAP products
    Check installed programs for SAP GUI versions 6.40 or 7.10, or SAP TabOne version 7.0.0.16. Use: `reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" /s | findstr /i "sap"` or check Program Files for SAP folders.
    Affected if Any affected SAP product version is installed on the system
  5. Verify presence of affected Servantix product
    Check for TSC2 Help Desk version 4.18. Look in Program Files for Servantix or TSC2 directories, or check Add/Remove Programs.
    Affected if TSC2 Help Desk version 4.18 is installed
  6. Confirm Internet Explorer ActiveX enablement for the control
    If the controls are present, check if they can be loaded in IE. In IE, go to Internet Options > Security > Custom Level > ActiveX controls and scripts. The attack vector is malicious web content triggering the AddTab method.
    Affected if The controls are registered and IE is configured to allow ActiveX controls from trusted or local intranet zones

The system is likely affected if c1sizer.ocx or sizerone.ocx exists with version 8.0.20081.140 OR any affected SAP/Servantix product is installed, especially if Internet Explorer can load these ActiveX controls.

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 or remove the affected ActiveX controls (c1sizer.ocx and sizerone.ocx) from vulnerable systems. If the controls are required, apply vendor patches from ComponentOne. Alternatively, set the 'Kill Bit' in the Windows registry to prevent the controls from loading in Internet Explorer.

Fix this in Sizerone Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-4827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-4827 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