Trust management is a popular technique for implementing information security, and specifically for access control policies. All data sources of an application are be classified into groups with varying degrees of trust. When doing this, it is imperative to ensure that trusted sources cannot be spoofed. This spoofing can be done in many ways:
Reflection attack. Principal Spoof. JSON Hijacking. Registry Poisoning. MITM. XSS. Attackers that are identified as trusted users or that are in a trusted zone with bad authentication techniques can do all sorts of things, depending on the services, such as:
Sniffing. Data tampering. Code Injection. DoS.
Darío can exploit the trust the application places in a source of data (e.g. user-definable data, manipulation of locally stored data, alteration to state data on a client device, lack of verification of identity during data validation such as Darío can pretend to be Colin)
Owasp ASVS (4.0): 1.12.2 ,5.1.3 ,9.2.3 ,12.2.1 ,12.3.1-12.3.3 ,12.4.2 ,12.5.2 ,14.5.3
Capec: 12 ,51 ,57 ,90 ,111 ,145 ,194 ,195 ,202 ,218 ,463
Owasp SCP: 2,19,92,95,180
Owasp Appsensor: IE4,IE5
Safecode: 14
ASVS V1.12 - Secure File Upload Architectural Requirements
ASVS V5.1 - Input Validation Requirements
ASVS V9.2 - Server Communications Security Requirements
ASVS V12.2 - File Integrity Requirements
ASVS V12.3 - File execution Requirements
ASVS V12.4 - File Storage Requirements
ASVS V12.5 - File Download Requirements
ASVS V14.5 - Validate HTTP Request Header Requirements
Session Hijacking (Man-in-the-Middle)
Loading comments 0%