dbcve.org
VxworksOperating system · Windriver

CVE-2013-0716

MEDIUM · 5.0 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 →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The web server in Wind River VxWorks 5.5 through 6.9 allows remote attackers to cause a denial of service (daemon crash) via a crafted URI.

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 confidence

The web server component in Wind River VxWorks versions 5.5 through 6.9 contains a denial of service vulnerability where processing a specially crafted URI causes the web server daemon to crash. This is a remote attack vector requiring no authentication.

MitigationApply available patches from Wind River for the affected VxWorks versions, or upgrade to a patched version. If patching is not immediately feasible, restrict network access to the web server or disable it if not essential.

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
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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
    Check the system version through the VxWorks boot line, kernel configuration, or system information interface. Common methods include examining /b or using the VxWorks command line 'version' or 'sysShow' commands.
    Affected if The version falls within 6.5, 6.6, 6.7, 6.8, or 6.9
  2. Confirm web server component is present
    Verify whether the VxWorks HTTP server (httpd) is included in the build and running on the system. Check running processes or inetd configuration for httpd.
    Affected if The web server daemon is present and active on the system
  3. Determine network accessibility
    Check if port 80 or the configured HTTP server port is listening and accessible from network interfaces. Use netstat or similar tools to inspect bound ports.
    Affected if The web server is bound to a network-accessible IP address and port

You are affected if VxWorks version 6.5, 6.6, 6.7, 6.8, or 6.9 is running with the HTTP server enabled and exposed to network access.

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

Apply available patches from Wind River for the affected VxWorks versions, or upgrade to a patched version. If patching is not immediately feasible, restrict network access to the web server or disable it if not essential.

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0716 — 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-0716 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