Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T ticket
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,809
    • Issues 1,809
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • ticket
  • Issues
  • #202

Closed
Open
Created Feb 10, 2022 by Administrator@rootMaintainer

attSensitiveInHtmlComments

Created by: armorcodegithubapp[bot]

Threat Class :Information Leakage Reason :AppScan discovered HTML comments containing what appears to be sensitive information. Technical Description :Many web application programmers use HTML comments to help debug the application when needed. While adding general comments is very useful, some programmers tend to leave important data, such as: filenames related to the web application, old links or links which were not meant to be browsed by users, old code fragments, etc. An attacker who finds these comments can map the application's structure and files, expose hidden parts of the site, and study the fragments of code to reverse engineer the application, which may help develop further attacks against the site. Risk :It is possible to gather sensitive information about the web application such as usernames, passwords, machine name and/or sensitive file locations

Mitigation: [1] Do not leave any vital information such as filenames or file paths in HTML comments. [2] Remove traces of previous (or future) site links in the production site comments. [3] Avoid placing sensitive information in HTML comments. [4] Make sure that HTML comments do not include source code fragments. [5] Make sure that no vital information was left behind by programmers.

https://app.armorcode.com/#/findings/64244244

Assignee
Assign to
Time tracking