sec-notes
  • Whoami
  • WEP-Pen
    • Reconnaissance
    • Enumeration
    • OWSAP TOP 10
      • Injection
        • Cross Site Scripting
          • Cross Site Scripting
          • Exploitation
          • Protections
        • SQL Injection
          • SQL Injection Overview
        • NoSQL Injection
        • CRLF Injection
        • XML Injection
      • Broken Access Control
        • Path Traversal
        • Sensitive Cookie with Improper SameSite Attribute
        • Link Following
        • Incorrect Default Permissions
        • Information disclosure
        • CSRF
          • csrf checklist
        • 403 bypass
        • Exposure of WSDL File Containing Sensitive Information
        • bussiness logic checklist
        • 2FA bypass checklist
        • admin panal checklist
        • idor checklist
        • Authentication checklist
        • reset_password_checklist
        • ATO
      • Cryptographic Failures
        • Cryptographic Failure
        • Weak Encoding for Password
        • Improper Following of a Certificate's Chain of Trust
          • Understanding Digital Certificates : Self-Signed and CA-Signed Certificate **
          • Transport Layer Security (TLS) and SSL **
        • Clear Text Transmission Of Sensitive Data
          • SSLStripping **
      • Insecure Design
      • Security Misconfiguration
        • CORS Miscofigration
        • Mail Server Misconfiguration
      • Vulnerable and Outdated Components
        • Using Components with Known Vulnerabilities
      • Identification and Authentication Failures
        • JWT Hacking
        • SAML Authentication bypass
      • Software and Data Integrity Failures
        • mass assignment
        • PostMessage Vulnerabilities
          • PostMessage Vulnerabilities
          • Blocking main page to steal postmessage
          • Bypassing SOP with Iframes - part 1
          • Bypassing SOP with Iframes - part 2
          • Steal postmessage modifying iframe location
      • Security Logging and Monitoring Failures
      • Server-Side Request Forgery (SSRF)
        • SSRF
    • Checklists
      • aem misconfiguration
      • exif_geo
      • xss
      • Session Management
      • Authorization
      • cookie
      • Django
      • Symfony
      • json
      • bypass rate limit
      • Rce
      • Register Page
  • API-Pen
    • API Discovry
    • Reverse Engineering API Documentation
    • Excessive Data Exposure
    • Vulnerability Scanning
    • API Authentication Attacks
      • Classic Authentication Attacks
      • API Token Attacks
    • API Authorization Attacks
      • Broken Object Level Authorization (BOLA)
      • Broken Function Level Authorization
    • Improper Assets Management
    • Mass Assignment
    • SSRF
    • Injection Attacks in API
    • Evasive Maneuvers
    • GraphQL Vulnerabilities
  • NET-Pen
    • Active Directory Pentesting
      • Active Directory Components
      • Initial Attack Vectors
        • LLMNR Poisoning
        • SMB Relay Attacks
        • IPv6 Attacks ( IPv6 DNS Takeover )
        • Printer Hacking
        • Methodology
        • Some Other Attacks
          • Zerologon (CVE-2020-1472)
          • PrintNightmare (CVE-2021-1675)
      • Post-Compromise Attacks
        • Pass Attacks
        • Kerberoasting Attack
        • Token Impersonation Attack
        • LNK File Attack
        • GPP / cPassword Attacks
        • Mimikatz
        • Methodology
      • We've Compromised the Domain
        • Dumping the NTDS.dit
        • Golden Ticket Attacks
        • Methodology
      • Case Study
      • Password Attacks
    • Attack Vectors by Port
      • FTP 21
      • SSH 22
      • Telnet 23 - 2323
      • SMTP 25
      • DNS 53
      • Kerberos 88
      • POP 110-995
      • RPC 111
      • Ident 113
      • NNTP 119
      • NetBIOS 137-138
      • SMB / Samba 135-139, 445
      • MSRPC 135
      • SNMP 161
      • LDAP 389,636
      • Modbus 502
      • OpenSSL 1337
      • Ms-SQL 1433
      • Oracle Listener 1521 1522 1529
      • NFS 2049
      • MySql 3306
      • RDP 3389
      • ADB Android Debug Bridge 5555
      • WinRM 5985 5986
      • VNC 5800 5900
      • Redis 6379
      • Unreal IRC 6667
      • Tomcat 8080
      • MongoDB 27017
      • http 80
    • Network basics
    • Information Gathering
    • Privilege Escalation
      • Windows Privilege Escalation
      • Linux Privilege Escalation
  • write-ups
    • How i found a Privilege Escalation via Impersonation Features feature
    • How I was able to discover ATO Via IDOR vulnerability
    • Easy full Account Takeover via Facebook OAuth Misconfiguration
Powered by GitBook
On this page
  • Step 1: Navigate through the login page.
  • Step 2: Navigate to /assets.
  • Step 3: Inspect the database file.
  • Step 4: Crack the hash
  • Step 5: Login with the derived credentials.
  1. WEP-Pen
  2. OWSAP TOP 10
  3. Cryptographic Failures

Cryptographic Failure

this lab covers a lot of basic cwes like CWE-327, CWE-759, CWE-916, CWE-319, CWE-523

PreviousCryptographic FailuresNextWeak Encoding for Password

Last updated 1 day ago

To better understand Cryptographic Failures, I will walk you through the Cryptographic Failures module in TryHackMe’s OWASP Top 10 room. In this scenario, we will analyze a vulnerable "Sense and Sensitivity" website.

Step 1: Navigate through the login page.

View the source code of the login page.

The developer has left a comment revealing that the database is stored in the /assets directory.

Step 2: Navigate to /assets.

There is, in fact, a web application database (webapp.db) stored in the /assets directory. Databases stored as files are known as ‘flat-file’ databases.

Step 3: Inspect the database file.

Click on the file to download it.

Determine the file type.

file webapp.db

The database is a SQlite database

Dump the database

sqlite3 webapp.db

Dump the tables.

.tables

Dump users.

PRAGMA table_info(users);
SELECT * FROM users;

We now have access to usernames and password hashes. Following the order, the second column contains the usernames, and the third column contains the password hashes.

Username:admin 
Password Hash:6eea9b7ef19179a06954edd0f6c05ceb

Step 4: Crack the hash

Crack the hash using CrackStation.

The hash has been identified as an MD5 hash and successfully cracked to reveal the plaintext password ‘qwertyuiop’.

Step 5: Login with the derived credentials.

Navigate back to the login page and use the credentials.

Username: admin
Password: qwertyuiop

We now have admin access and can perform actions, including adding and deleting users.

Cryptographic flaws, including the use of weak algorithms such as MD5, coupled with data exposure, can result in the compromise of sensitive information and systems.