dbcve.org
FusionforgeApplication

CVE-2015-0850

HIGH · 10.0 CVSS v2.0 Published 2015-06-02
Fix available
A fix is available. Upgrade to after 6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Git plugin for FusionForge before 6.0rc4 allows remote attackers to execute arbitrary code via an unspecified parameter when creating a secondary Git repository.

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

The Git plugin for FusionForge before version 6.0rc4 contains an arbitrary code execution vulnerability. Attackers can exploit unspecified parameters during secondary Git repository creation to inject and execute malicious code remotely.

MitigationUpgrade FusionForge to version 6.0rc4 or later which contains the patched Git plugin. If immediate upgrade is not feasible, disable the Git plugin to prevent exploitation.

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
FusionforgeApplication
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. Identify FusionForge installation and version
    Check the installed FusionForge version by looking at the package manager (dpkg, rpm) or the web interface footer. Common paths: /usr/share/fusionforge/etc/config.ini or check packages with 'dpkg -l | grep fusionforge' or 'rpm -qa | grep fusionforge'.
    Affected if The installed version is less than 6.0rc4 (including all 5.x and early 6.0 versions before rc4).
  2. Locate the Git plugin configuration
    The Git plugin is typically found at /usr/share/fusionforge/plugins/git/ or within the FusionForge web root under plugins/. Check for the presence of the git plugin directory.
    Affected if The Git plugin directory exists and contains the plugin files, indicating it is installed.
  3. Verify if Git plugin is enabled
    Check FusionForge configuration files (usually in /etc/fusionforge/config.ini or the site's local configuration) for the plugins section. Look for an entry like 'enabled_plugins' or similar that includes 'git'. Alternatively, access the Site Admin > Plugin Manager page in the web interface.
    Affected if The Git plugin is listed as enabled in the FusionForge configuration.
  4. Check Git plugin version
    If the plugin directory exists, look for a version file within the git plugin directory, or check the plugin's init.php or similar entry point for version information. The plugin version may be embedded in the code or a separate VERSION file.
    Affected if The Git plugin version cannot be determined or is earlier than the version bundled with 6.0rc4.

A user is affected if FusionForge with the Git plugin enabled is installed at a version earlier than 6.0rc4.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0
Vendor patch fusionforge.org →
Interim mitigation

Upgrade FusionForge to version 6.0rc4 or later which contains the patched Git plugin. If immediate upgrade is not feasible, disable the Git plugin to prevent exploitation.

Recommended fix High confidence

FusionForge 6.0rc4 or later stable release

  1. 1. Back up your current FusionForge installation and database before proceeding with any upgrade.
  2. 2. Identify your current FusionForge version by checking the /opt/fusionforge/version file or the admin interface.
  3. 3. Download FusionForge 6.0rc4 or a stable release after 6.0 from the official FusionForge download page.
  4. 4. Stop the FusionForge services (apache/httpd, database) before upgrading.
  5. 5. Follow the official FusionForge upgrade documentation for your distribution (Debian, RHEL/CentOS, etc.).
  6. 6. Run the database migration scripts included in the upgrade package.
  7. 7. Start the FusionForge services and verify the Git plugin is functioning correctly.
  8. 8. Test that creating a secondary Git repository works without issues.
Caveat Review FusionForge release notes for any configuration or plugin API changes between your version and 6.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fusionforge 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-2015-0850 — 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-2015-0850 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