nerdexam
CompTIA

PT0-002 · Question #159

A penetration tester was able to gather MD5 hashes from a server and crack the hashes easily with rainbow tables. Which of the following should be included as a recommendation in the remediation…

The correct answer is A. Stronger algorithmic requirements. Since MD5 hashes were easily cracked with rainbow tables, the primary recommendation should be to implement stronger cryptographic algorithms for password storage. This involves moving away from weak hashing functions like MD5 to more robust, salted, and iterated hashing…

Attacks and Exploits

Question

A penetration tester was able to gather MD5 hashes from a server and crack the hashes easily with rainbow tables. Which of the following should be included as a recommendation in the remediation report?

Options

  • AStronger algorithmic requirements
  • BAccess controls on the server
  • CEncryption on the user passwords
  • DA patch management program

How the community answered

(23 responses)
  • A
    78% (18)
  • B
    4% (1)
  • C
    4% (1)
  • D
    13% (3)

Why each option

Since MD5 hashes were easily cracked with rainbow tables, the primary recommendation should be to implement stronger cryptographic algorithms for password storage. This involves moving away from weak hashing functions like MD5 to more robust, salted, and iterated hashing algorithms.

AStronger algorithmic requirementsCorrect

The fact that MD5 hashes were easily cracked with rainbow tables indicates that the system is using a weak, unsalted hashing algorithm for password storage. The most direct and effective remediation is to recommend stronger algorithmic requirements, specifically transitioning to modern, cryptographically secure hashing functions that incorporate salting and iteration (e.g., Argon2, bcrypt, scrypt) to make rainbow table attacks and brute-force cracking significantly more difficult.

BAccess controls on the server

While access controls are important for general server security, they do not directly address the weakness in the password hashing mechanism itself.

CEncryption on the user passwords

Passwords should be *hashed*, not encrypted, for storage. If passwords were encrypted, the encryption key would still need to be stored, creating a single point of failure and allowing decryption back to plaintext.

DA patch management program

A patch management program addresses vulnerabilities in software, not the fundamental weakness of using a cryptographically weak hashing algorithm for passwords.

Concept tested: Password hashing best practices - strong algorithms

Source: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/how-domain-controllers-store-passwords

Topics

#Hashing algorithms#Password security#Rainbow tables#Vulnerability remediation

Community Discussion

No community discussion yet for this question.

Full PT0-002 Practice