Skip to content

Conversation

@sydseter
Copy link
Collaborator

@sydseter sydseter commented Jul 15, 2025

This PR closes #2585

Description

See issue for details


[x] I have read the contributing guidelines.

Guidelines for Pull Requests (you can delete this section after reading):

  • Please ensure that your content follows the style guide.
  • If you are working on Porting MASTG v1 Tests to v2, refer to this document.
  • If you are working on new MASWE, tests, or demos, refer to this document.

@sydseter sydseter changed the title Fixes #2585 Fixes OWASP/mastg#2585 [MASWE-0021] Weak Hashing Jul 15, 2025
@cpholguera cpholguera requested a review from Diolor October 29, 2025 09:27
Comment on lines 38 to 40
- **Loss of Integrity and authenticity**: A deprecated, risky or broken hashing algorithm, may allow an attacker to compromise the integrity and authenticity of data at rest and in transit.
- **Loss of Confidentiality**: A deprecated, risky or broken hashing algorithm may expose the preimage (input) and in so doing break the confidentiality.
- **Risk of Brute-Force Attacks**: A deprecated, risky or broken hashing is susceptible to brute-force attacks.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brute force is an attack that could result in "an impact". Let's focus on integrity solely here

sydseter and others added 4 commits November 3, 2025 12:50
Co-authored-by: Dionysis Lorentzos <ddl449@gmail.com>
Co-authored-by: Dionysis Lorentzos <ddl449@gmail.com>
Updated language for clarity and consistency regarding hashing algorithms and their vulnerabilities.
@sydseter sydseter requested a review from Diolor November 3, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[MASWE-0021] Weak Hashing

2 participants