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.
Potential Impact
Confidentiality
Read Application Data, Read Files or Directories
Mitigations & Prevention
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.
Related Weaknesses
Frequently Asked Questions
What is CWE-527?
CWE-527 (Exposure of Version-Control Repository to an Unauthorized Control Sphere) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. 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.
How can CWE-527 be exploited?
Attackers can exploit CWE-527 (Exposure of Version-Control Repository to an Unauthorized Control Sphere) to read application data, read files or directories. This weakness is typically introduced during the Operation phase of software development.
How do I prevent CWE-527?
Key mitigations include: 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 upd
What is the severity of CWE-527?
CWE-527 is classified as a Variant-level weakness (Low-Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.