dbcve.org
StatusnetApplication · Status

CVE-2011-3370

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-12
Fix available
A fix is available. Upgrade to 0.9.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
statusnet before 0.9.9 has XSS

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

Statusnet before version 0.9.9 contains a Cross-Site Scripting (XSS) vulnerability. The exact attack vector, affected input fields, and exploitation method are not specified in the available description, but XSS vulnerabilities typically allow attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpgrade Statusnet to version 0.9.9 or later to resolve the XSS vulnerability. If upgrading is not immediately possible, implement output encoding and input validation as interim measures.

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
StatusnetApplication
Affected:< 0.9.9= 1.0.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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 Statusnet version file
    Check the root directory of your Statusnet installation for a version file (often named 'version' or 'VERSION') or inspect the main configuration file for a version string.
    Affected if The displayed version is less than 0.9.9 or equals 1.0.0
  2. Check the admin interface for version info
    Log into the Statusnet admin panel and navigate to the site information or about page which typically displays the installed version.
    Affected if The reported version is below 0.9.9 or is exactly 1.0.0
  3. Inspect the HTML source for version metadata
    View the source of any Statusnet page and search for version indicators in meta tags, footer comments, or script tags that may contain version numbers.
    Affected if The version found in the source code is < 0.9.9 or = 1.0.0
  4. Query the database for version record
    If you have database access, check the config or version table for a stored version value.
    Affected if The stored version is less than 0.9.9 or equals 1.0.0

Your environment is affected if the installed Statusnet version is any release before 0.9.9 or specifically version 1.0.0.

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
Upgrade available Upgrade to 0.9.9 or later
Fixed in 0.9.9
Interim mitigation

Upgrade Statusnet to version 0.9.9 or later to resolve the XSS vulnerability. If upgrading is not immediately possible, implement output encoding and input validation as interim measures.

Fix this in Statusnet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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