dbcve.org
SmarterstatsApplication · Smartertools

CVE-2011-2158

HIGH · 10.0 CVSS v2.0 Published 2011-05-20
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
The SmarterTools SmarterStats 6.0 web server sends incorrect Content-Type headers for certain resources, which might allow remote attackers to have an unspecified impact by leveraging an interpretation conflict involving (1) Admin/frmSite.aspx, (2) Admin/frmSites.aspx, (3) Admin/frmViewReports.aspx, (4) App_Themes/AboutThisFolder.txt, (5) Client/frmViewReports.aspx, (6) Temp/AboutThisFolder.txt, (7) default.aspx, (8) login.aspx, or (9) certain .jpg URIs under Temp/. NOTE: it is possible that only clients, not the SmarterStats product, could be affected by this issue.

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 confidence

SmarterStats 6.0 web server sends incorrect Content-Type headers for multiple resources (ASPX pages, TXT files, JPG images), causing interpretation conflicts where browsers or clients may process files differently based on mismatched MIME types. This MIME sniffing vulnerability could enable cross-site scripting or other client-side attacks.

MitigationConfigure correct MIME type mappings in the web server to ensure proper Content-Type headers are sent for all resources; consider upgrading to a supported version if vendor updates are available.

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
SmarterstatsApplication
Affected:= 6.0

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

AV:N/AC:L/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. Confirm SmarterStats installation
    Identify if SmarterStats web server is installed and running on the target system. Check for SmarterStats processes or services, and note the web server port (typically 9999 or 443).
    Affected if SmarterStats is installed and running as a web server on the system.
  2. Verify the installed version
    Access the SmarterStats web interface or check the installed software version through the administration panel or system registry. Confirm the exact version number is 6.0.
    Affected if The installed version is exactly 6.0 (the only affected version per the CVE).
  3. Test ASPX page Content-Type headers
    Make an HTTP request to any .aspx page hosted by SmarterStats and inspect the Content-Type header in the response. Compare it against the expected MIME type for ASPX files (should be 'text/html' or 'application/aspx').
    Affected if The Content-Type header is missing, incorrect, or differs from the expected MIME type for ASPX files.
  4. Test TXT file Content-Type headers
    Request any .txt file from the SmarterStats web server and examine the Content-Type header returned in the HTTP response.
    Affected if The Content-Type header is missing, incorrect, or shows an unexpected MIME type (should be 'text/plain').
  5. Test JPG image Content-Type headers
    Request any .jpg or .jpeg image from the SmarterStats web server and inspect the Content-Type header in the response.
    Affected if The Content-Type header is missing, incorrect, or shows an unexpected MIME type (should be 'image/jpeg').

If SmarterStats version 6.0 is installed and its web server returns mismatched or incorrect Content-Type headers for ASPX, TXT, or JPG files, the environment is affected by this CVE.

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

Configure correct MIME type mappings in the web server to ensure proper Content-Type headers are sent for all resources; consider upgrading to a supported version if vendor updates are available.

Fix this in Smarterstats Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2158 — 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-2011-2158 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