JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc
Ada


ADA.IO.TAINT.FNAME : Tainted Filename (Ada)

This warning class corresponds to a GNAT SAS message. The CodeSonar analysis results may include warnings of this class if your CodeSonar project includes Ada components.

Summary

A file operation identifies a file by name, but the name string may have been tainted.

This warning class corresponds to the GNAT SAS Path_traversal.

Properties

Class Name Tainted Filename (Ada)
Significance security
Mnemonic ADA.IO.TAINT.FNAME
Categories
CWE CWE:22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
  CWE:73 External Control of File Name or Path
  CWE:99 Improper Control of Resource Identifiers ('Resource Injection')
  CWE:610 Externally Controlled Reference to a Resource in Another Sphere
  CWE:641 Improper Restriction of Names for Files and Other Resources
OWASP-2017 OWASP-2017:A1 Injection
  OWASP-2017:A5 Broken access control
OWASP-2021 OWASP-2021:A1 Broken access control
  OWASP-2021:A3 Injection
  OWASP-2021:A4 Insecure design
OWASP-2025 OWASP-2025:A01 Broken Access Control
  OWASP-2025:A05 Injection
  OWASP-2025:A06 Insecure Design
Availability Available for Ada only.
Enabling Checks for this warning class are enabled by default. To disable them, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += discard class="Tainted Filename (Ada)"

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.

 

To report problems with this documentation, please visit https://support.codesecure.com/.