ElinksApplication

CVE-2006-5925

HIGH · 7.5 CVSS v2.0 Published 2006-11-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Links web browser 1.00pre12 and Elinks 0.9.2 with smbclient installed allows remote attackers to execute arbitrary code via shell metacharacters in an smb:// URI, as demonstrated by using PUT and GET statements.

Technical summary

dbcve analysis · high confidence

Command injection vulnerability in Links and Elinks browsers when processing smb:// URIs. The browsers pass unsanitized URI content directly to the smbclient program without sanitizing shell metacharacters, allowing remote attackers to inject and execute arbitrary shell commands.

MitigationUpgrade to a patched version of Links or Elinks that properly sanitizes smb:// URI parameters before passing them to smbclient, or remove/disable smbclient if the SMB protocol handler is not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ElinksApplication

Affected:= 0.9.2

LinksApplication

Affected:= 1.00pre12

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if Links or Elinks browser is installed

Run 'which links' or 'which elinks' to locate the executable, or check package manager output (dpkg -l | grep -E 'links|elinks' or rpm -qa | grep -E 'links|elinks')

Affected if Either Links or Elinks is present on the system
Determine the installed version of the browser

Run 'links -version' or 'elinks -version' and compare the output version number to the affected ranges (Elinks = 0.9.2, Links = 1.00pre12)

Affected if The version matches exactly 0.9.2 for Elinks or 1.00pre12 for Links (note: the '=' notation indicates the exact version is affected)
Verify if smbclient is installed and accessible

Run 'which smbclient' or check if /usr/bin/smbclient or /usr/local/bin/smbclient exists

Affected if smbclient is present on the system - the vulnerability requires smbclient to be invoked with unsanitized input
Check if the SMB protocol handler is configured or used

Look for smb configuration in the browser config files (~/.elinks/elinks.conf, ~/.links/links.cfg, /etc/elinks.conf, /etc/links.cfg) for smb:// protocol settings, or attempt to visit an smb:// URL in the browser to confirm handler existence

Affected if The browser has an active smb:// protocol handler configured or functional

You are affected if you have Links or Elinks at exactly version 0.9.2 or 1.00pre12 respectively, with smbclient installed and the smb:// protocol handler enabled - the command injection occurs when processing smb:// URIs through smbclient.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to a patched version of Links or Elinks that properly sanitizes smb:// URI parameters before passing them to smbclient, or remove/disable smbclient if the SMB protocol handler is not required.

Fix this in Elinks 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 help mitigating

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-2006-5925 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-5925 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-5925?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 8.3%

Affects: Elinks

Remediation

A high-priority fix

Fix this in Elinks 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2006-5925 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References