Openshift OriginApplication · Redhat
CVE-2014-0084
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 · uneditedRuby gem openshift-origin-node before 2014-02-14 does not contain a cronjob timeout which could result in a denial of service in cron.daily and cron.weekly.
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 openshift-origin-node Ruby gem before February 2014 lacks a timeout mechanism for scheduled cron jobs (cron.daily and cron.weekly). Without a timeout, these cron tasks can run indefinitely and consume system resources, leading to denial of service.
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
Openshift OriginApplication
< 2014-02-14CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Identify openshift-origin-node installationRun 'rpm -qa | grep openshift-origin-node' or check gem list for openshift-origin-nodeAffected if The package is not installed or the command returns no output, they are not using this component
-
Determine installed versionRun 'rpm -q --qf "%{VERSION}-%{RELEASE}" openshift-origin-node' or 'gem list openshift-origin-node' to get the exact version numberAffected if The version is earlier than 2014-02-14 release or cannot be determined (indicating an old unpatched version)
-
Locate cron job configuration filesCheck /etc/cron.daily/ and /etc/cron.weekly/ directories, or examine /etc/crontab for entries calling openshift utilitiesAffected if Cron jobs for openshift (openshift cron.daily or cron.weekly) are present and configured to run
-
Verify cron job execution contextExamine the cron job scripts in /etc/cron.daily/ and /etc/cron.weekly/ for any timeout or timeoutctl wrapper, or check if the scripts have inherent timeout logicAffected if The cron scripts lack any timeout mechanism, timeoutctl wrapper, or timeout command surrounding the execution
-
Confirm cron scheduler is activeVerify cron daemon is running with 'service crond status' or 'systemctl status crond'Affected if Cron daemon is active and the affected cron.daily/cron.weekly jobs will execute without timeout protection
User is affected if openshift-origin-node version is before 2014-02-14 AND cron jobs (cron.daily or cron.weekly) are configured and active without timeout controls.
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 data2014-02-14
Implement timeout controls for cron.daily and cron.weekly jobs, or upgrade openshift-origin-node to a version released after 2014-02-14 that includes timeout functionality.
Fix this in Openshift Origin
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0084 — 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-0084 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