BE-Hacktive
HackTricksTwitterLinkedInSponsorWebsite
French
French
  • BE-Hacktive
  • A propos de l'auteur et du projet
  • Table des matières
  • Contact
  • 🎬Synopsis
    • Technologie dans le temps
    • Cybersécurité
    • CVE
  • 🏆Eskooly - CVE
    • ESKOOLY (FR version)
    • ESKOOLY (EN version)
    • CVE-2024-27709 - SQL Injection in Eskooly Web Product v.3.0
    • ESkooly - Broken Authentication
      • CVE-2024-27710 - Privilege Escalation via Authentication Mechanism in Eskooly Web Product <= v3.0
      • CVE-2024-27711 - User Enumeration via Sign-up Process in Eskooly Web Product <= v3.0
      • CVE-2024-27712 - User Enumeration via Account Settings in Eskooly Web Product <= v3.0
    • CVE-2024-27713 - Protection mechanism Failure in Eskooly Web Product <= v3.0
    • CVE-2024-27715 - Inadequate Password Update Verification in Eskooly Web Product <= v3.0
    • CVE-2024-27716 - Cross-site Scripting (XSS) in Eskooly Web Product <= v3.0
    • CVE-2024-27717 - Cross-Site Request Forgery (CSRF) in Eskooly Web Product <= v3.0
  • 🚨Capsule 1 - Sensibilisation
    • Phishing
      • Phishing - Origines
      • Phishing - Evolution
      • Phishing - Statistiques
      • Phishing - Techniques
      • Phishing - Protection
    • Malware
      • Malware - Origines
      • Malware - Evolution
      • Malware - Catégories
      • Malware - Ransomware
    • Passwords - Mots de passe
      • Passwords - Origines
      • Passwords - Evolution de l'authentification
      • Passwords - Statistiques
      • Passwords - Protégez-vous
  • 🧨Capsule 2 - Ethical Hacking
    • Définition et Méthodologie
  • 🧰Capsule 3 - Outils
    • Burp Suite
      • Installation
      • Intercepter le trafic HTTP avec Burp Proxy
      • Définir le périmètre
      • Intruder et Repeater
  • Capsule 2 - Ethical Hacking
    • Page 1
  • 📖Articles
    • Cybersécurité 2023: 5 menaces majeures et comment s'en protéger
    • Suis-je victime des fuites de données ?
    • LOG4J: La librairie vulnérable qui secoue la planète
    • LOG4SHELL: VENI,VIDI,VICI
    • Protéger votre enfant en ligne: Conseils pour le "Safer Internet Day"
    • ChatGPT: Révolution ou menace ?
    • Le FBI démantèle Raptor Train : Un Botnet Chinois qui a Infecté 260 000 Appareils IoT dans le monde!
  • 🗞️News
    • Exploitation active des vulnérabilités de TP-Link, d'Apache et d'Oracle détectées
    • Microsoft insiste sur l'urgence de patcher les serveurs Exchange en local
Powered by GitBook
On this page
  • Description
  • Related Findings
  • Technical Details
  • Risk
  • Impact
  • Likelihood
  • Recommendation
  • References
  1. Eskooly - CVE

CVE-2024-27713 - Protection mechanism Failure in Eskooly Web Product <= v3.0

PreviousCVE-2024-27712 - User Enumeration via Account Settings in Eskooly Web Product <= v3.0NextCVE-2024-27715 - Inadequate Password Update Verification in Eskooly Web Product <= v3.0

Description

Eskooly web application does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Related Findings

  • Security Headers Misconfiguration

Technical Details

The vulnerability arises from flaws in the sign-up process that allow attackers to manipulate account settings during registration. This can lead to unauthorized privilege escalation, enabling attackers to register accounts with higher privileges than intended.

  1. 8 Security headers are missing

  1. No cookie protection

Risk

Impact

Medium.

The absence of critical security headers such as X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security, and others significantly increases the website's vulnerability to several types of attacks. Without X-Frame-Options, the site is susceptible to clickjacking attacks, where an attacker could trick a user into clicking on something different from what the user perceives, potentially leading to unauthorized actions. The lack of X-Content-Type-Options exposes the site to MIME type confusion attacks, where the browser might execute non-executable MIME types, leading to cross-site scripting (XSS) or other code execution attacks. Furthermore, not implementing Strict-Transport-Security can allow attackers to intercept or alter communications between the user and the website, compromising confidentiality and integrity. Each missing header contributes to an overall weakened security posture, making sensitive data and user interactions more prone to interception and manipulation.

Likelihood

High.

The likelihood of an exploit resulting from these misconfigurations is high, considering the prevalent use of automated tools and scripts that detect and exploit such vulnerabilities. The specific details of the website's traffic, user base, and content type can further influence this likelihood. High-profile or high-traffic websites are particularly attractive targets, increasing the probability of attacks. The simplicity of executing attacks like clickjacking, MIME sniffing, or SSL stripping (in the absence of HSTS) means that even less sophisticated attackers could successfully compromise the website's security. Moreover, the absence of policies like Permissions-Policy and Cross-Origin-Resource-Policy opens up additional avenues for unauthorized access and data theft, making it more likely that such vulnerabilities will be exploited if not promptly and adequately addressed.

Recommendation

References

🏆
OWASP: Secure Headers Project
CWE-693: Protection Mechanism Failure
OWASP: HTTP Security Response Headers Cheat Sheet