dbcve.org
VxworksOperating system · Windriver

CVE-2013-0713

MEDIUM · 6.8 CVSS v2.0 Published 2013-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote authenticated users to cause a denial of service (daemon outage) via a crafted pty 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 · high confidence

IPSSH (the SSH server) in Wind River VxWorks versions 6.5 through 6.9 contains a vulnerability in pty (pseudo-terminal) request handling. An authenticated remote attacker can send a specially crafted pty request to cause the SSH daemon to crash, resulting in denial of service.

MitigationRestrict SSH access to trusted authenticated users only; contact Wind River for available patches; consider disabling pty allocation in sshd_config if not required for legitimate operations.

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
VxworksOperating system
Affected:= 6.5= 6.6= 6.7= 6.8= 6.9

CVSS 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
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VxWorks version
    Run the command to display the VxWorks kernel version, typically via 'version' or checking system information files
    Affected if The version shown is 6.5, 6.6, 6.7, 6.8, or 6.9
  2. Confirm IPSSH is installed
    Check for the presence of the SSH server binary or service, typically via 'ps' or by listing /sbin or /usr/sbin for sshd-related binaries
    Affected if IPSSH or sshd is present and running on the system
  3. Verify pty allocation is enabled
    Inspect the SSH daemon configuration file (sshd_config) for the 'AllowTcpForwarding' or 'Pty' directive; if present, confirm it is not explicitly disabled
    Affected if pty allocation is allowed (not set to 'no' or disabled) in the SSH configuration

A system is affected if it runs VxWorks version 6.5 through 6.9, has IPSSH enabled, and has pty allocation permitted in the SSH configuration, allowing an authenticated attacker to crash the daemon via a crafted pty request.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict SSH access to trusted authenticated users only; contact Wind River for available patches; consider disabling pty allocation in sshd_config if not required for legitimate operations.

Fix this in Vxworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0713 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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