CVE-2007-6167
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 yast2-core in SUSE Linux might allow local users to execute arbitrary code by creating a malicious yast2 module in the current working directory.
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 · moderate confidenceUntrusted search path vulnerability in yast2-core allows local users to execute arbitrary code by placing a malicious yast2 module in the current working directory, which gets loaded when an administrator runs yast2 with that directory as cwd.
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 dataall versionsCVSS 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.
-
Verify yast2-core package is installedRun 'rpm -q yast2-core' or 'zypper se yast2-core' to list the installed yast2-core packageAffected if The package is installed - all versions are affected by this vulnerability
-
Identify yast2 module search pathRun 'yast2 --help' or examine the binary to determine the default module search path. Check configuration files in /etc/yast2/ and /usr/share/yast2/ for module path settingsAffected if The search path includes the current working directory or allows relative module loading
-
Check for world-writable directories with yast2 modulesSearch for .ycp or .so module files in common directories: 'find /tmp /var/tmp /home -name "*.ycp" -o -name "*.so" 2>/dev/null' and inspect /usr/lib/yast2/ for module locationsAffected if Modules exist in directories where unprivileged users can write, enabling them to place malicious modules
-
Test module loading behavior from untrusted directoryCreate a test directory, place a test module file in it, change to that directory, and run 'yast2' to see if it attempts to load modules from the current working directoryAffected if yast2 loads or attempts to load modules from the current working directory without absolute path verification
-
Review yast2 execution environmentRun 'env' command after using yast2, and check if YAST_MODULE_PATH or similar environment variables include relative paths or the current working directoryAffected if Environment variables or configuration allows loading modules from relative or current working directory paths
If yast2-core is installed and its module loading mechanism includes the current working directory in its search path, the system is vulnerable to local privilege escalation via malicious modules.
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 dataEnsure yast2 is run from secure directories with proper access controls, or apply vendor patches that enforce secure module loading using absolute paths and exclude the current working directory from the module search path.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6167 — 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-2007-6167 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