dbcve.org
FusionforgeApplication

CVE-2013-1423

MEDIUM · 6.9 CVSS v2.0 Published 2013-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
(1) contrib/gforge-3.0-cronjobs.patch, (2) cronjobs/homedirs.php, (3) deb-specific/fileforge.pl, (4) deb-specific/group_dump_update.pl, (5) deb-specific/ssh_dump_update.pl, (6) deb-specific/user_dump_update.pl, (7) plugins/scmbzr/common/BzrPlugin.class.php, (8) plugins/scmcvs/common/CVSPlugin.class.php, (9) plugins/scmcvs/cronjobs/cvs.php, (10) plugins/scmcvs/cronjobs/ssh_create.php, (11) plugins/scmgit/common/GitPlugin.class.php, (12) plugins/scmsvn/common/SVNPlugin.class.php, (13) plugins/wiki/cronjobs/create_groups.php, (14) utils/cvs1/cvscreate.sh, and (15) utils/include.pl in FusionForge 5.0, 5.1, and 5.2 allows local users to change arbitrary file permissions, obtain sensitive information, and have other unspecified impacts via a (1) symlink or (2) hard link attack on certain files.

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

Multiple files in FusionForge 5.0-5.2 (cronjobs, plugins, and utilities) contain symlink/hard link vulnerabilities that allow local users to manipulate arbitrary file permissions, access sensitive information, or cause unspecified impacts through improper validation of file operations.

MitigationReview and harden all identified files (cronjobs, plugins, utilities) to validate file targets before operations, avoid following symlinks in file manipulation routines, and implement proper permission controls on world-writable directories.

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:= 5.0= 5.1= 5.2

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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/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 version
    Run command to retrieve installed FusionForge version, such as checking package manager output (dpkg -l fusionforge or rpm -qi fusionforge) or querying the application itself
    Affected if Version is 5.0, 5.1, or 5.2
  2. Locate FusionForge cronjobs
    Inspect /etc/cron.d/fusionforge, /etc/cron.daily/fusionforge, or similar cron directories for FusionForge-related scripts
    Affected if Cronjob files exist and perform file operations without validating symlink/hard link targets
  3. Identify installed FusionForge plugins
    List contents of /usr/share/fusionforge/plugins/ or the equivalent plugin installation directory
    Affected if Any plugins are installed that perform file manipulation operations
  4. Check for world-writable directories
    Find directories owned by the FusionForge user with world-writable permissions (find /var/lib/fusionforge -type d -perm -002)
    Affected if World-writable directories exist that the FusionForge process can access, allowing symlink attack vectors
  5. Review utility scripts for file operations
    Examine scripts in FusionForge bin/ or scripts/ directories for file operations (cp, mv, chmod, chown) that lack symlink validation
    Affected if Utilities perform file operations without checking if the target is a symlink or hard link before acting on it

Environment is affected if FusionForge version 5.0-5.2 is installed AND world-writable directories exist that can be exploited through symlink/hard link attacks in cronjobs, plugins, or utilities.

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

Review and harden all identified files (cronjobs, plugins, utilities) to validate file targets before operations, avoid following symlinks in file manipulation routines, and implement proper permission controls on world-writable directories.

Fix this in Fusionforge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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