DerScanner
Home / Vulnerability Database / PL or SQL : Cookie: broad domain
PL/SQL

PL or SQL : Cookie: broad domain

Classification

OWASP Top 10 2013
A2-Broken Authentication and Session Management
OWASP Mobile Top 10 2016
M2-Insecure Data Storage
OWASP Top 10 2017
A2-Broken AuthenticationA3-Sensitive Data Exposure
OWASP Top 10 2021
A2-Cryptographic FailuresA4-Insecure DesignA7-Identification and Authentication Failures
PCI DSS 4.0
6.2.4
HIPAA
§164.312 (e)(1)
CWE
CWE-1028

Overview

Cookie domain is set broadly. Broad domain (e.g., .example.com) is insecure, because in this case the vulnerability in one application could endanger other applications in the same domain.

Sensitive Data Exposure vulnerabilities take the third place in the “OWASP Top 10 2017” web-application vulnerabilities ranking.

References

  1. OWASP Top 10 2013-A5-Security Misconfiguration
  2. Origin Cookies: Session Integrity for Web Applications (pdf)
  3. OWA_COOKIE - docs.oracle.com
  4. OWASP Top 10 2017 A2-Broken Authentication
  5. CWE CATEGORY: OWASP Top Ten 2017 Category A2 - Broken Authentication
MEDIUM

DerScanner Severity Score

Do you want to fix PL or SQL : Cookie: broad domain in your application?

See also

PL/SQL

PL or SQL : Open redirect

PL/SQL

PL or SQL : Cross-site scripting (XSS)

PL/SQL

PL or SQL : Weak hashing algorithm