Insecure encryption algorithm - AES

Description

The source code uses RSA/ECB/PKCS1Padding and AES/CBC/PKCS5PADDING encryption and other references use CTR or CFB which are considered insecure.

Impact

Decrypt the information encrypted with the algorithm because it has vulnerabilities that make it easily breakable.

Recommendation

Only secure encryption with secure algorithms such as RSA/NONE/OAEPwithSHA-256andMGF1Padding or use implementations with the GCM mode encryption algorithm.

Threat

Attacker with access to the code.

Expected Remediation Time

⌚ 30 minutes.

Score

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

Base

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

Temporal

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

Result

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

Requirements

• 148.Set minimum size of asymmetric encryption
• 150.Set minimum size for hash functions

Fixes

• Ruby
• Elixir
• Python
• C-Sharp
• TypeScript
• Java
• Swift
• Go
• Scala

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.