Skip to main content

Business information leak - JFROG

Description

Through the credentials obtained in the code, access is obtained to external resources where there are binaries of which, if reverse engineering is applied, it is possible to find information burned in the code, such as access credentials to the Active directory.

Impact

Use the collected information for further attacks, such as AD information to access organizational information.

Recommendation

  • According to the classification of the information found, establish the necessary controls so that the information is accessible only to the indicated persons.
  • Sensitive information should not be stored in binaries or source code.

Threat

External attacker with access to business information.

Expected Remediation Time

⌚ 60 minutes.

Score

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

Base

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

Temporal

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

Result

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

Code Examples

Compliant code

The access keys to sensitive resources are stored correctly encrypted

jfrog.accesskey   = ${access_key}
artifact.password = ENC(something-base64-encoded-but-encrypted)

Non compliant code

Access keys directly stored in the source code

jfrog.accesskey   = "AKIA0000000000000000"
artifact.password = "123"

Requirements