Bonobo Git ServerApplication · Bonobogitserver

CVE-2019-11218

HIGH · 8.8 CVSS v3.0 Published 2019-04-24
Fix available
A fix is available. Upgrade to 6.5.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper handling of extra parameters in the AccountController (User Profile edit) in Jakub Chodounsky Bonobo Git Server before 6.5.0 allows authenticated users to gain application administrator privileges via additional form parameter submissions.

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

A parameter tampering vulnerability in the AccountController of Bonobo Git Server allows authenticated users to escalate privileges to administrator by submitting extra form parameters during profile edits. The application fails to whitelist or properly validate allowed parameters, enabling mass assignment of sensitive roles.

MitigationUpgrade Bonobo Git Server to version 6.5.0 or later, which implements proper parameter validation and prevents unauthorized privilege escalation.

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
Bonobo Git ServerApplication
Affected:< 6.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify Bonobo Git Server installation version
    Locate the Bonobo Git Server installation directory and check the version. Common locations include the bin folder where Bonobo.Git.Server.dll resides; right-click the DLL, select Properties, and view the File Version or Product Version. Alternatively, check the web.config file for version information.
    Affected if The installed version is earlier than 6.5.0 (e.g., 6.4.0, 6.3.0, etc.)
  2. Verify AccountController handles profile edits
    Confirm that the Bonobo Git Server web application is running and accessible. Navigate to the user profile editing functionality (typically /Account/Edit or /Account/Profile). This is where the parameter tampering occurs.
    Affected if The profile editing interface is accessible to authenticated users and accepts form submissions.
  3. Check for parameter validation on profile submissions
    Inspect the AccountController.cs source code (if available in the deployment) or use a web proxy to capture a profile edit request. Observe whether the application accepts only whitelisted parameters or allows arbitrary form fields.
    Affected if The application accepts and processes additional form parameters beyond the expected fields (e.g., role, IsAdmin, or similar role-related parameters).
  4. Confirm user has authenticated access
    Log into the Bonobo Git Server with a standard non-administrator user account and verify the ability to access profile editing.
    Affected if An authenticated (non-admin) user can access and submit the profile edit form.

A user is affected if they are running Bonobo Git Server version below 6.5.0 AND have authenticated non-administrator users who can access profile editing functionality, as the missing parameter validation allows role escalation.

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 6.5.0 or later
Fixed in 6.5.0
Interim mitigation

Upgrade Bonobo Git Server to version 6.5.0 or later, which implements proper parameter validation and prevents unauthorized privilege escalation.

Fix this in Bonobo Git Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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