Description
The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
Version control repositories such as CVS or git store version-specific metadata and other details within subdirectories. If these subdirectories are stored on a web server or added to an archive, then these could be used by an attacker. This information may include usernames, filenames, path root, IP addresses, and detailed “diff” data about how files have been changed – which could reveal source code snippets that were never intended to be made public.
Modes of Introduction:
– Operation
Related Weaknesses
Consequences
Confidentiality: Read Application Data, Read Files or Directories
Potential Mitigations
Phase: Operation, Distribution, System Configuration
Description:
Recommendations include removing any CVS directories and repositories from the production server, disabling the use of remote CVS repositories, and ensuring that the latest CVS patches and version updates have been performed.