CVE-2014-4867
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 · uneditedCryoserver Security Appliance 7.3.x uses weak permissions for /etc/init.d/cryoserver, which allows local users to gain privileges by leveraging access to the support account and running the /bin/cryo-mgmt program.
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 confidenceCryoserver Security Appliance 7.3.x contains a local privilege escalation vulnerability stemming from weak file permissions on /etc/init.d/cryoserver. Users with access to the support account can run /bin/cryo-mgmt to leverage these improper permissions and gain elevated privileges.
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= 7.3.0= 7.3.1= 7.3.2= 7.3.3= 7.3.4CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/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.
-
Identify Cryoserver appliance and versionRun 'lsb_release -a' or check system hostname/documentation to confirm this is a Cryoserver Security Appliance. Then check the installed version using 'dpkg -l | grep cryoserver' or 'rpm -qa | grep cryoserver' depending on the package manager.Affected if The installed version is 7.3.0, 7.3.1, 7.3.2, 7.3.3, or 7.3.4
-
Verify /etc/init.d/cryoserver existsRun 'ls -la /etc/init.d/cryoserver' to check if the init script file exists on the system.Affected if The file /etc/init.d/cryoserver exists on the system
-
Check file permissions on /etc/init.d/cryoserverRun 'ls -l /etc/init.d/cryoserver' and examine the permission bits (the first column). Look for world-readable or group-readable permissions beyond root-only.Affected if Permissions allow non-root users (other or group) to read or write the file (e.g., permissions like 644, 664, 755, 775, or similar)
-
Verify /bin/cryo-mgmt existsRun 'ls -la /bin/cryo-mgmt' to check if the management binary exists on the system.Affected if The file /bin/cryo-mgmt exists on the system
-
Check support account accessCheck for the existence of a support account by examining /etc/passwd or using 'id support' or 'getent passwd support'. Also check sudo or su permissions for this account.Affected if A support account exists and has access to /bin/cryo-mgmt or elevated privileges
A user is affected if they are running Cryoserver Security Appliance version 7.3.0-7.3.4, the /etc/init.d/cryoserver file has weak permissions allowing non-root access, and a support account exists with access to /bin/cryo-mgmt that can be exploited for privilege escalation.
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 dataRestrict file permissions on /etc/init.d/cryoserver to root-only or appropriate system group, and review access controls for the support account and /bin/cryo-mgmt program following least-privilege principles.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4867 — 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-2014-4867 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