CVE-2017-17531
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 · uneditedgozilla.c in GNU GLOBAL 4.8.6 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL.
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 confidenceThe gozilla.c component in GNU GLOBAL 4.8.6 uses the BROWSER environment variable to determine which browser program to execute but fails to validate or sanitize the value before passing it to the system. An attacker who can control the BROWSER environment variable (e.g., via crafted URLs processed by the application) can inject arbitrary command-line arguments into the browser execution, leading to arbitrary command execution.
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= 4.8.6CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GNU GLOBAL versionRun 'global --version' or 'gtags --version' to determine the installed versionAffected if Version is 4.8.6 exactly (note: only this specific version is affected)
-
Locate the gozilla.c componentFind gozilla.c in the source code or check if gozilla utility exists (typically in /usr/bin/gozilla or similar paths)Affected if The gozilla binary is present and executable in the environment
-
Verify BROWSER environment variable usageRun 'env | grep BROWSER' or inspect if the application sets/uses the BROWSER environment variable when invoking gozillaAffected if The BROWSER environment variable is set and used by gozilla
-
Check for user control of BROWSER variableReview application configuration or scripts that invoke GNU GLOBAL to determine if any user-supplied input (such as URLs, file paths, or configuration values) can influence the BROWSER environment variableAffected if User-controlled data can flow into or set the BROWSER environment variable before gozilla is invoked
You are affected if you are running GNU GLOBAL version 4.8.6, use the gozilla component, and have the BROWSER environment variable set with user-controllable values that reach gozilla.
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 dataValidate and sanitize the BROWSER environment variable value before use, or implement allowlist-based validation to ensure only trusted browser executables are invoked.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2017-17531 — 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-2017-17531 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