CVE-2010-2929
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 · uneditedUntrusted search path vulnerability in hsolinkcontrol in hsolink 1.0.118 allows local users to gain privileges via a modified PATH environment variable, which is used during execution of the (1) route, (2) mv, and (3) cp programs, a different vulnerability than CVE-2010-1671.
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 hsolinkcontrol component in hsolink 1.0.118 contains an untrusted search path vulnerability where it executes route, mv, and cp programs without using absolute paths. A local attacker can modify the PATH environment variable to point to malicious versions of these executables, achieving privilege escalation.
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= 1.0.118CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if hsolink is installedLook for hsolink installation directories or check package management systems. Common paths may include /usr/bin/hsolink, /usr/local/bin/hsolink, or search using 'find / -name hsolink* 2>/dev/null'Affected if hsolink is not found on the system - not vulnerable
-
Verify the installed hsolink versionRun 'hsolink --version' or check the version information of the hsolink binary. Alternatively, check the package metadata or binary file version if the command is unavailableAffected if The version is exactly 1.0.118 - potentially vulnerable
-
Locate the hsolinkcontrol componentSearch for the hsolinkcontrol binary or script using 'find / -name hsolinkcontrol 2>/dev/null' or check in the same directory as the main hsolink binaryAffected if hsolinkcontrol component exists and is executable - vulnerable component present
-
Inspect hsolinkcontrol for relative command executionExamine the hsolinkcontrol binary or script (if text-based) for calls to route, mv, or cp commands without full absolute paths. Use 'strings' on the binary or decompile/disassemble to inspect system call behaviorAffected if The component calls route, mv, or cp without absolute paths (e.g., uses 'route' instead of '/bin/route') - vulnerability is present
-
Check execution context and privilegesDetermine if hsolinkcontrol runs with elevated privileges by checking file permissions (ls -la hsolinkcontrol) and whether it is invoked via setuid/sudo or by privileged servicesAffected if hsolinkcontrol runs as root or with elevated privileges - exploitation could lead to privilege escalation
The system is affected only if hsolink version 1.0.118 is installed with the hsolinkcontrol component present and it executes route, mv, or cp commands without absolute paths while running with elevated privileges.
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 relative command invocations with absolute paths or sanitize the PATH environment variable before execution. Alternatively, remove or disable the hsolinkcontrol component if not required.
- 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-2010-2929 — 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-2929 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