CVE-2013-0714
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 · uneditedIPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote attackers to execute arbitrary code or cause a denial of service (daemon hang) via a crafted public-key authentication request.
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 confidenceThe IPSSH (SSH server) component in Wind River VxWorks versions 6.5 through 6.9 contains a vulnerability in its public-key authentication handling that allows remote attackers to execute arbitrary code or cause a denial of service by sending specially crafted public-key authentication requests.
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= 6.5= 6.6= 6.7= 6.8= 6.9CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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.
-
Identify VxWorks versionRun 'version' command or check system information files to determine the installed VxWorks version numberAffected if Version is 6.5, 6.6, 6.7, 6.8, or 6.9
-
Confirm IPSSH component is presentCheck if the SSH server daemon (IPSSH) is installed and running on the system; look for sshd process or IPSSH serviceAffected if IPSSH/SSH daemon is installed and active
-
Verify public-key authentication is enabledExamine SSH server configuration for public-key authentication settings; check if authorized_keys or similar public-key authentication mechanisms are configuredAffected if Public-key authentication is enabled in SSH configuration
System is affected if running VxWorks 6.5-6.9 with IPSSH component active and public-key authentication enabled
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.
dbcve · scopedApply vendor patches for VxWorks if available; otherwise, restrict network access to SSH services using firewalls or network segmentation, and consider disabling public-key authentication if not required.
VxWorks 6.9 or later (contact Wind River for specific patch for your version)
- Contact Wind River customer support to obtain the specific patch for CVE-2013-0714 for your VxWorks version
- Apply the Wind River patch to the IPSSH (SSH server) component
- After patching, verify the SSH server version to confirm the fix is applied
- Test SSH public-key authentication to ensure functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2013-0714 — 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-2013-0714 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