Lack of data validation - OTP

Description

There is no evidence of validation of the values sent in the tokenCode parameter to complete the request, allowing random values to be used in multiple attempts.

Impact

Perform the account creation process without knowing the generated token.

Recommendation

• Validate on the server side that the token sent by the user is the one generated for the request.
• Validate that the token generated is used only once.

Threat

External attacker authenticated.

Expected Remediation Time

⌚ minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the src.

Base

• Attack vector: N
• Attack complexity: L
• Privileges required: L
• User interaction: N
• Scope: U
• Confidentiality: N
• Integrity: L
• Availability: N

Temporal

• Exploit code madurity: X
• Remediation level: X
• Report confidence: X

Result

• Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:X/RL:X/RC:X
• Score:
  • Base: 4.3
  • Temporal: 4.3
• Severity:
  • Base: Medium
  • Temporal: Medium

Requirements

• 173.Discard unsafe inputs
• 320.Avoid client-side control enforcement
• 357.Use stateless session tokens

Fixes

• Elixir
• Scala
• Python
• Ruby
• Go
• Dart
• Java
• C-Sharp
• PHP
• TypeScript

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.