dbcve.org
GfaxApplication · Debian

CVE-2007-2839

HIGH · 7.2 CVSS v2.0 Published 2007-07-05
Fix available
A fix is available. Upgrade to after 0.4.2 or later.
See remediation →
77/100
Remediation priority · High
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
gfax 0.4.2 and probably other versions creates temporary files insecurely, which allows local users to execute arbitrary commands via unknown vectors.

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

gfax 0.4.2 creates temporary files insecurely, allowing local users to execute arbitrary commands through insecure temporary file handling (likely TOCTOU race conditions or predictable filenames).

MitigationReplace insecure temporary file creation with secure methods (e.g., mkstemp, O_EXCL flag) and ensure proper file permissions; restrict file system access where possible.

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
GfaxApplication
Affected:<= 0.4.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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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. Check if gfax is installed
    Run 'dpkg -l | grep gfax' or 'which gfax' to determine if the gfax package is present on the system
    Affected if gfax is installed and its version is 0.4.2 or lower
  2. Verify the installed gfax version
    Run 'dpkg -s gfax' or check the package version through the package manager to confirm the exact version number
    Affected if The installed version is 0.4.2 or any version up to and including 0.4.2
  3. Inspect temporary file creation patterns in gfax
    Examine the gfax binary or scripts for use of predictable temporary file names (e.g., using mktemp without O_EXCL, or hardcoded paths in /tmp)
    Affected if The code uses insecure temporary file methods such as predictable filenames in /tmp without proper safeguards
  4. Check /tmp directory permissions and accessibility
    Run 'ls -la /tmp' to verify that /tmp has proper sticky-bit permissions (1777) and is not world-writable in a way that allows symlink attacks
    Affected if The /tmp directory allows unprivileged users to manipulate files in ways that could exploit TOCTOU race conditions in gfax

A system is affected if gfax version 0.4.2 or lower is installed and uses insecure temporary file handling that could be exploited through local file system manipulation.

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 a release after 0.4.2
Interim mitigation

Replace insecure temporary file creation with secure methods (e.g., mkstemp, O_EXCL flag) and ensure proper file permissions; restrict file system access where possible.

Fix this in Gfax Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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