Skip to main content

Inappropriate coding practices - Wildcard export

Description​

When exporting libraries, the wildcard operator (asterisk) is used, which exports all the functions of that library. This is a bad practice that complicates the use and maintenance of the module.

Impact​

  • Export functions and procedures that will not be used.
  • Cause suboptimal performance of the application.

Recommendation​

Explicitly export the libraries and packages necessary for the correct operation of the application.

Threat​

Attacker authenticated in the application from the Internet.

Expected Remediation Time​

⌚ 30 minutes.

Score​

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

Base​

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

Temporal​

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

Result​

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

Code Examples​

Compliant code​

Explicitly export the functions and variable required for the application

//Module code...
export { myFunction as function,
  myVariable as variable};

Non compliant code​

A module includes a wildcard export

//Module code...

export *

Requirements​

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.