Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE CATEGORY:Comprehensive Categorization: File Handling
Category ID:1404
Vulnerability Mapping:Prohibited
Status:Incomplete
DetailsContent HistoryObserved CVE ExamplesReports
▼Summary

Weaknesses in this category are related to file handling.

▼Membership
NatureMappingTypeIDName
MemberOfProhibitedV1400Comprehensive Categorization for Software Assurance Trends
HasMemberAllowedB22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
HasMemberAllowedB23Relative Path Traversal
HasMemberAllowedV24Path Traversal: '../filedir'
HasMemberAllowedV25Path Traversal: '/../filedir'
HasMemberAllowedV26Path Traversal: '/dir/../filename'
HasMemberAllowedV27Path Traversal: 'dir/../../filename'
HasMemberAllowedV28Path Traversal: '..\filedir'
HasMemberAllowedV29Path Traversal: '\..\filename'
HasMemberAllowedV30Path Traversal: '\dir\..\filename'
HasMemberAllowedV31Path Traversal: 'dir\..\..\filename'
HasMemberAllowedV32Path Traversal: '...' (Triple Dot)
HasMemberAllowedV33Path Traversal: '....' (Multiple Dot)
HasMemberAllowedV34Path Traversal: '....//'
HasMemberAllowedV35Path Traversal: '.../...//'
HasMemberAllowedB36Absolute Path Traversal
HasMemberAllowedV37Path Traversal: '/absolute/pathname/here'
HasMemberAllowedV38Path Traversal: '\absolute\pathname\here'
HasMemberAllowedV39Path Traversal: 'C:dirname'
HasMemberAllowedV40Path Traversal: '\\UNC\share\name\' (Windows UNC Share)
HasMemberAllowedB41Improper Resolution of Path Equivalence
HasMemberAllowedV42Path Equivalence: 'filename.' (Trailing Dot)
HasMemberAllowedV43Path Equivalence: 'filename....' (Multiple Trailing Dot)
HasMemberAllowedV44Path Equivalence: 'file.name' (Internal Dot)
HasMemberAllowedV45Path Equivalence: 'file...name' (Multiple Internal Dot)
HasMemberAllowedV46Path Equivalence: 'filename ' (Trailing Space)
HasMemberAllowedV47Path Equivalence: ' filename' (Leading Space)
HasMemberAllowedV48Path Equivalence: 'file name' (Internal Whitespace)
HasMemberAllowedV49Path Equivalence: 'filename/' (Trailing Slash)
HasMemberAllowedV50Path Equivalence: '//multiple/leading/slash'
HasMemberAllowedV51Path Equivalence: '/multiple//internal/slash'
HasMemberAllowedV52Path Equivalence: '/multiple/trailing/slash//'
HasMemberAllowedV53Path Equivalence: '\multiple\\internal\backslash'
HasMemberAllowedV54Path Equivalence: 'filedir\' (Trailing Backslash)
HasMemberAllowedV55Path Equivalence: '/./' (Single Dot Directory)
HasMemberAllowedV56Path Equivalence: 'filedir*' (Wildcard)
HasMemberAllowedV57Path Equivalence: 'fakedir/../realdir/filename'
HasMemberAllowedV58Path Equivalence: Windows 8.3 Filename
HasMemberAllowedB59Improper Link Resolution Before File Access ('Link Following')
HasMemberAllowedC61UNIX Symbolic Link (Symlink) Following
HasMemberAllowedV62UNIX Hard Link
HasMemberAllowedV64Windows Shortcut Following (.LNK)
HasMemberAllowedV65Windows Hard Link
HasMemberAllowedB66Improper Handling of File Names that Identify Virtual Resources
HasMemberAllowedV67Improper Handling of Windows Device Names
HasMemberAllowedV69Improper Handling of Windows ::DATA Alternate Data Stream
HasMemberAllowedV72Improper Handling of Apple HFS+ Alternate Data Stream Path
Nature: MemberOf
Mapping: Prohibited
Type: View
ID: 1400
Name: Comprehensive Categorization for Software Assurance Trends
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 22
Name: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 23
Name: Relative Path Traversal
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 24
Name: Path Traversal: '../filedir'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 25
Name: Path Traversal: '/../filedir'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 26
Name: Path Traversal: '/dir/../filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 27
Name: Path Traversal: 'dir/../../filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 28
Name: Path Traversal: '..\filedir'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 29
Name: Path Traversal: '\..\filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 30
Name: Path Traversal: '\dir\..\filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 31
Name: Path Traversal: 'dir\..\..\filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 32
Name: Path Traversal: '...' (Triple Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 33
Name: Path Traversal: '....' (Multiple Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 34
Name: Path Traversal: '....//'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 35
Name: Path Traversal: '.../...//'
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 36
Name: Absolute Path Traversal
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 37
Name: Path Traversal: '/absolute/pathname/here'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 38
Name: Path Traversal: '\absolute\pathname\here'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 39
Name: Path Traversal: 'C:dirname'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 40
Name: Path Traversal: '\\UNC\share\name\' (Windows UNC Share)
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 41
Name: Improper Resolution of Path Equivalence
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 42
Name: Path Equivalence: 'filename.' (Trailing Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 43
Name: Path Equivalence: 'filename....' (Multiple Trailing Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 44
Name: Path Equivalence: 'file.name' (Internal Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 45
Name: Path Equivalence: 'file...name' (Multiple Internal Dot)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 46
Name: Path Equivalence: 'filename ' (Trailing Space)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 47
Name: Path Equivalence: ' filename' (Leading Space)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 48
Name: Path Equivalence: 'file name' (Internal Whitespace)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 49
Name: Path Equivalence: 'filename/' (Trailing Slash)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 50
Name: Path Equivalence: '//multiple/leading/slash'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 51
Name: Path Equivalence: '/multiple//internal/slash'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 52
Name: Path Equivalence: '/multiple/trailing/slash//'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 53
Name: Path Equivalence: '\multiple\\internal\backslash'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 54
Name: Path Equivalence: 'filedir\' (Trailing Backslash)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 55
Name: Path Equivalence: '/./' (Single Dot Directory)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 56
Name: Path Equivalence: 'filedir*' (Wildcard)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 57
Name: Path Equivalence: 'fakedir/../realdir/filename'
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 58
Name: Path Equivalence: Windows 8.3 Filename
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 59
Name: Improper Link Resolution Before File Access ('Link Following')
Nature: HasMember
Mapping: Allowed
Type: Compound
ID: 61
Name: UNIX Symbolic Link (Symlink) Following
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 62
Name: UNIX Hard Link
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 64
Name: Windows Shortcut Following (.LNK)
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 65
Name: Windows Hard Link
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 66
Name: Improper Handling of File Names that Identify Virtual Resources
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 67
Name: Improper Handling of Windows Device Names
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 69
Name: Improper Handling of Windows ::DATA Alternate Data Stream
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 72
Name: Improper Handling of Apple HFS+ Alternate Data Stream Path
▼Vulnerability Mapping Notes
Usage:Prohibited
Reason:
Rationale:

This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves [REF-1330].

Comments:

See member weaknesses of this category.

▼Notes
▼Taxonomy Mappings
Taxonomy NameEntry IDFitEntry Name
▼References
Reference ID: REF-1330
Title: CVE --> CWE Mapping Guidance - Quick Tips
Version: v4.15
Author: MITRE
Publication:
Publisher:
Edition:
URL:https://cwe.mitre.org/documents/cwe_usage/quick_tips.html
URL Date:
Day:25
Month:03
Year:2021
Details not found