Symlink Following Vulnerability in Gitingest

Gitingest through version 0.3.1 is affected by a symlink following vulnerability within the ingest_query single-file blob ingestion process. This vulnerability allows an unauthenticated attacker to bypass intended file access restrictions by committing a symbolic link to a public source code repository. When an attacker submits the URL of this malicious blob to the Gitingest service, the application follows the symlink during the ingestion process. Consequently, the server reads and returns the contents of the target file to the user, provided the file is accessible to the system user running the Gitingest service. The impact of this file disclosure is limited to files up to 10 MB in size. This flaw presents a significant risk to the confidentiality of sensitive system data, including configuration files and environment variables, if the service is configured with excessive filesystem permissions.

Impact

Successful exploitation allows unauthenticated attackers to read arbitrary files from the hosting server. This could lead to the exposure of sensitive configuration files, source code, credentials, or environment secrets. The exposure is limited to files readable by the Gitingest process, with a size cap of 10 MB per request.

Recommendation

• Upgrade the Gitingest service to a version beyond 0.3.1 immediately to remediate the underlying symlink following vulnerability.
• Apply the principle of least privilege by running the Gitingest service process under a dedicated, low-privilege user account with restricted filesystem access.
• Implement outbound network filtering to prevent the Gitingest server from communicating with unauthorized or untrusted external git repositories.
• Conduct a review of server logs for anomalous file read requests or recurring ingestion errors originating from unknown or public repository sources.