CWE-67: Improper Handling of Windows Device Names Skip to content

Security weakness

CWE-67 Improper Handling of Windows Device Names

A variant-level weakness that can lead to private data exposed and downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-67?

Improper Handling of Windows Device Names: The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular.

Business impact

What CWE-67 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • DoS: Crash, Exit, or Restart
  • Read Application Data
  • Other

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Crash, Exit, or Restart
  • Read Application Data
  • Other

Free security check

Is CWE-67 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-67

Improper Handling of Windows Device Names

The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file.

Weakness ID
CWE-67
Type
Variant
Status
Incomplete
Likelihood of exploit
High
Applies to
Windows
Introduced during
Implementation, Operation

Prevention

How to fix CWE-67, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Implementation

    • Be familiar with the device names in the operating system where your system is deployed. Check input for these device names.

Detection and evidence

How CWE-67 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

Real vulnerabilities it caused

  • CVE-2002-0106Server allows remote attackers to cause a denial of service via a series of requests to .JSP files that contain an MS-DOS device name.
  • CVE-2002-0200Server allows remote attackers to cause a denial of service via an HTTP request for an MS-DOS device name.
  • CVE-2002-1052Product allows remote attackers to use MS-DOS device names in HTTP requests to cause a denial of service or obtain the physical path of the server.
  • CVE-2001-0493Server allows remote attackers to cause a denial of service via a URL that contains an MS-DOS device name.
  • CVE-2001-0558Server allows a remote attacker to create a denial of service via a URL request which includes a MS-DOS device name.
  • CVE-2000-0168Microsoft Windows 9x operating systems allow an attacker to cause a denial of service via a pathname that includes file device names, aka the "DOS Device in Path Name" vulnerability.

How we fix it

From finding to fixed: how Codefreex closes CWE-67

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-67: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-67?

CWE-67, “Improper Handling of Windows Device Names”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file.

How serious is CWE-67?

MITRE rates the likelihood of exploit as High. It can affect availability, confidentiality, other, with impacts such as dos: crash, exit, or restart, read application data, other. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-67?

Be familiar with the device names in the operating system where your system is deployed. Check input for these device names.

Can Codefreex check my site for CWE-67?

Yes. A senior engineer reviews your site, store or app for CWE-67 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-67 affect?

MITRE lists it as applicable to Windows. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-67 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.