CVE-2011-0650
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 · uneditedCross-site request forgery (CSRF) vulnerability in Greenbone Security Assistant (GSA) before 2.0+rc3 allows remote attackers to hijack the authentication of users for requests that send email via an OMP request to OpenVAS Manager. NOTE: this issue can be leveraged to bypass authentication requirements for exploiting CVE-2011-0018.
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 confidenceCSRF vulnerability in Greenbone Security Assistant (GSA) versions before 2.0+rc3 allows remote attackers to hijack authenticated user sessions to send email via OMP (OpenVAS Management Protocol) requests. The flaw can also be chained with CVE-2011-0018 to bypass authentication requirements.
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<= 2.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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Identify GSA versionLocate and inspect the Greenbone Security Assistant installation to determine its version number. Common methods include checking the package manager (dpkg, rpm, or similar), the web interface version displayed in the footer, or the application's About/Help page.Affected if The installed version is 2.0 or any version prior to 2.0+rc3 (such as 1.x releases or early 2.0 beta/rc versions).
-
Confirm GSA web interface is activeVerify that the Greenbone Security Assistant web interface is running and accessible. This is typically accessed over HTTP/HTTPS on the configured web server port.Affected if The GSA web interface is publicly or semi-publicly accessible, increasing exposure to CSRF attacks from malicious sites.
-
Verify OMP protocol is in useCheck if the OpenVAS Management Protocol (OMP) is being used for communication between GSA and the OpenVAS Manager. This can be confirmed by reviewing network traffic, configuration files, or observing OMP command usage within the web interface.Affected if OMP requests are processed by the GSA without proper anti-CSRF token validation, which is the attack vector for this vulnerability.
-
Check for anti-CSRF protectionInspect OMP request handling within GSA to determine whether anti-CSRF tokens or similar protections are implemented for OMP operations. This may require reviewing source code or observing request/response patterns when performing actions via the web interface.Affected if OMP requests do not require or validate anti-CSRF tokens, meaning authenticated users' sessions can be hijacked for unauthorized actions.
You are affected if GSA version 2.0 or earlier is installed and the web interface with OMP functionality is accessible, as these versions lack proper anti-CSRF token validation for OMP requests.
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 dataUpgrade to GSA version 2.0+rc3 or later, which should include proper anti-CSRF token validation for OMP requests.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0650 — 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-2011-0650 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