CWE-134: Use of Externally-Controlled Format String Skip to content

Security weakness

CWE-134 Use of Externally-Controlled Format String

A base-level weakness that can lead to private data exposed, data, pages or code changed 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-134?

Use of Externally-Controlled Format String: The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

Business impact

What CWE-134 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.

  • Read Memory
  • Modify Memory
  • Execute Unauthorized Code or Commands

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Modify Memory
  • Execute Unauthorized Code or Commands

Availability

Downtime and lost sales

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

  • Modify Memory
  • Execute Unauthorized Code or Commands

Free security check

Is CWE-134 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-134

Use of Externally-Controlled Format String

The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

Weakness ID
CWE-134
Type
Base
Status
Draft
Likelihood of exploit
High
Applies to
C, C++, Perl, Python
Introduced during
Implementation

Prevention

How to fix CWE-134, phase by phase

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

  1. 01

    Requirements

    • Choose a language that is not subject to this flaw.
  2. 02

    Implementation

    • Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings. [REF-116] [REF-117]
  3. 03

    Build and Compilation

    • Run compilers and linkers with high warning levels, since they may detect incorrect usage.

Detection and evidence

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

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

How it is detected

  • Automated Static AnalysisThis weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.
  • Black BoxSince format strings often occur in rarely-occurring erroneous conditions (e.g. for error message logging), they can be difficult to detect using black box methods. It is highly likely that many latent issues exist in executables that do not have associated source code (or equivalent source.
  • Automated Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Bytecode Weakness Analysis – including disassembler + source code weakness analysis Binary Weakness Analysis – including disassembler + source code weakness analysis Binary / Bytecode simple extractor – strings, ELF.
  • Manual Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Binary / Bytecode disassembler – then use manual analysis for vulnerabilities & anomalies
  • Dynamic Analysis with Automated Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Web Application Scanner Web Services Scanner Database Scanners

Real vulnerabilities it caused

  • CVE-2002-1825format string in Perl program
  • CVE-2001-0717format string in bad call to syslog function
  • CVE-2002-0573format string in bad call to syslog function
  • CVE-2002-1788format strings in NNTP server responses
  • CVE-2006-2480Format string vulnerability exploited by triggering errors or warnings, as demonstrated via format string specifiers in a .bmp filename.
  • CVE-2007-2027Chain: untrusted search path enabling resultant format string by loading malicious internationalization messages.

How we fix it

From finding to fixed: how Codefreex closes CWE-134

  1. 01

    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. 02

    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. 03

    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. 04

    Keep it fixed

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

FAQ

CWE-134: FAQs

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

What is CWE-134?

CWE-134, “Use of Externally-Controlled Format String”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

How serious is CWE-134?

MITRE rates the likelihood of exploit as High. It can affect confidentiality, integrity, availability, with impacts such as read memory, modify memory, execute unauthorized code or commands. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-134?

Choose a language that is not subject to this flaw. Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all.

Can Codefreex check my site for CWE-134?

Yes. A senior engineer reviews your site, store or app for CWE-134 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-134 affect?

MITRE lists it as applicable to C, C++, Perl, Python. 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-134 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.