Skip to main content

Inappropriate coding practices - invalid file

Description​

Files are stored in the repository that cannot be verified because their content is not compatible with their extension.

Impact​

  • Difficult security auditing process.
  • Cause an inadequate operation in the different applications that make use of it.

Recommendation​

  • Verify the identified files and adjust their content to their corresponding extension.

Threat​

Attacker authenticated from the Internet with access to the source code.

Expected Remediation Time​

⌚ 15 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: N
  • Availability: L

Temporal​

  • Exploit code madurity: U
  • Remediation level: U
  • Report confidence: R

Result​

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

Code Examples​

Compliant code​

Use of comments in json file.

[
  {
    "_comment": "comment text goes here...",
    "name": "example document",
    "int": 123,
    "notation": -123.123e-2,
    "unicode": "\u2665",
    "character": "0",
  },
]

Non compliant code​

Inappropriate use of comments in json file.

[
//This is a comment to be adjusted in production.
  {
    "name": "example document",
    "int": 123,
    "notation": -123.123e-2,
    "unicode": "\u2665",
    "character": "0",
  },
]

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.