CVE-2010-2449
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 · uneditedGource through 0.26 logs to a predictable file name (/tmp/gource-$UID.tmp), enabling attackers to overwrite an arbitrary file via a symlink attack.
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 confidenceGource through version 0.26 writes log files to a predictable location in /tmp using the naming pattern /tmp/gource-$UID.tmp, where $UID is the user's numeric ID. This predictable path enables local attackers to perform a symlink attack by pre-creating a symbolic link at that expected path pointing to a target file they wish to overwrite, causing gource to follow the symlink and write to the attacker's chosen file when it runs.
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<= 0.26CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Check installed Gource versionRun 'gource --version' or check your package manager for the installed gource package versionAffected if The version is 0.26 or lower (any version up to and including 0.26)
-
Identify if Gource log files are usedLook for any scripts or workflows that invoke gource with log file arguments, or check for existing files matching /tmp/gource-* pattern in /tmpAffected if You use Gource to generate or display version control logs (any log file usage)
-
Test for symlink vulnerability in /tmpAs the target user, verify whether a file at /tmp/gource-$(id -u).tmp can be pre-created; check if another local user could place a symlink at that pathAffected if Other local users have write access to /tmp and can create a symbolic link at /tmp/gource-YOUR_UID.tmp pointing to a file they wish to overwrite
-
Verify /tmp directory permissionsRun 'ls -ld /tmp' to check if the /tmp directory has sticky bit set (mode 1777)Affected if The /tmp directory allows untrusted users to create files or symlinks in it (missing sticky bit or overly permissive)
You are affected if you run Gource version 0.26 or lower and other local users can access or predict the /tmp/gource-$UID.tmp path where your numeric UID would be used.
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 dataReplace the predictable temporary file naming with a secure method such as using mktemp() to generate random file names, or using O_EXCL flag when creating the file to prevent symlink attacks. Alternatively, use a secure temporary directory with restricted permissions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2449 — 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-2010-2449 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