{'xhtml:p': 'An adversary spoofs metadata pertaining to a Version Control System (VCS) (e.g., Git) repository's commits to deceive users into believing that the maliciously provided software is frequently maintained and originates from a trusted source.'}
Description
Attack Execution Flow
4
1
Step 1
Explore[Identify target] The adversary must first identify a target repository for them to spoof. Typically, this will be a popular and widely used repository, as to increase the amount of victims a successful attack will exploit.
AI Translation
[Identifica obiettivo] L'attore malevolo deve prima identificare un repository target da impersonare. Tipicamente, si tratta di un repository popolare e ampiamente utilizzato, al fine di aumentare il numero di vittime che un attacco riuscito potrà sfruttare.
2
Step 2
Experiment[Create malicious repository] The adversary must create a malicious repository that imitates the legitimate repository being spoofed. This may include creating a username that closely matches the legitimate repository owner; creating a repository name that closely matches the legitimate repository name; uploading the legitimate source code; and more.
AI Translation
[Creare un repository dannoso] L'attaccante deve creare un repository dannoso che imiti quello legittimo che si intende spoofare. Ciò può includere la creazione di un nome utente che corrisponda strettamente a quello del proprietario del repository legittimo; la creazione di un nome di repository che corrisponda strettamente a quello del repository legittimo; il caricamento del codice sorgente legittimo; e altro ancora.
3
Step 3
Experiment[Spoof commit metadata] Once the malicious repository has been created, the adversary must then spoof the commit metadata to make the repository appear to be frequently maintained and originating from trusted sources.
Git Commit Timestamps: The adversary generates numerous fake commits while setting the 'GIT_AUTHOR_DATE' and 'GIT_COMMITTER_DATE' environment variables to a date which is to be spoofed.
Git Commit Contributors: The adversary obtains a legitimate and trusted user's email address and then sets this information via the 'git config' command. The adversary can then commit changes leveraging this username.
AI Translation
[Spoofing dei metadati del commit] Una volta creato il repository malevolo, l'attaccante deve quindi falsificare i metadati del commit per far sembrare che il repository venga mantenuto frequentemente e abbia origine da fonti affidabili.
Timestamp dei commit Git: l'attaccante genera numerosi commit falsi impostando le variabili di ambiente "GIT_AUTHOR_DATE" e "GIT_COMMITTER_DATE" su una data da falsificare.
Contributori dei commit Git: l'attaccante ottiene l'indirizzo email di un utente legittimo e affidabile e poi imposta queste informazioni tramite il comando "git config". L'attaccante può quindi effettuare commit sfruttando questo nome utente.
Attack Techniques
-
Git Commit Timestamps: The adversary generates numerous fake commits while setting the "GIT_AUTHOR_DATE" and "GIT_COMMITTER_DATE" environment variables to a date which is to be spoofed.
-
Git Commit Contributors: The adversary obtains a legitimate and trusted user's email address and then sets this information via the "git config" command. The adversary can then commit changes leveraging this username.IT: Timestamp dei commit Git: l'avversario genera numerosi commit falsi impostando le variabili di ambiente "GIT_AUTHOR_DATE" e "GIT_COMMITTER_DATE" a una data da falsificare.
4
Step 4
Exploit[Exploit victims] The adversary infiltrates software and/or system environments with the goal of conducting additional attacks.
Active: The adversary attempts to trick victims into downloading the malicious software by means such as phishing and social engineering.
Passive: The adversary waits for victims to download and leverage malicious software.
AI Translation
[Victime dell'exploit] L'avversario si infiltra in ambienti software e/o di sistema con l'obiettivo di condurre ulteriori attacchi.
Attivo: L'avversario tenta di ingannare le vittime inducendole a scaricare il software dannoso tramite metodi come phishing e social engineering.
Passivo: L'avversario attende che le vittime scarichino e sfruttino il software dannoso.
Attack Techniques
-
Active: The adversary attempts to trick victims into downloading the malicious software by means such as phishing and social engineering.
-
Passive: The adversary waits for victims to download and leverage malicious software.IT: Attivo: L'avversario tenta di ingannare le vittime inducendole a scaricare il software dannoso tramite metodi come phishing e social engineering.
Mitigations
6
After Downloading Open-Source Software, Ensure Integrity Values Have Not Changed.
Before Downloading Open-Source Software, Perform Precursory Metadata Checks To Determine The Author(S), Frequency Of Updates, When The Software Was Last Updated, And If The Software Is Widely Leveraged.
Before Executing Or Incorporating The Software, Leverage Automated Testing Techniques (E.G., Static And Dynamic Analysis) To Determine If The Software Behaves Maliciously.
Only Download Open-Source Software From Reputable Hosting Sites Or Package Managers.
Only Download Open-Source Software That Has Been Adequately Signed By The Developer(S). For Repository Commits/Tags, Look For The "Verified" Status And For Developers Leveraging "Vigilant Mode" (Github) Or Similar Modes.
Reference Vulnerability Databases To Determine If The Software Contains Known Vulnerabilities.
Consequences
Security Scopes Affected
Access Control
Accountability
Authorization
Integrity
Potential Impacts
Alter Execution Logic
Execute Unauthorized Commands
Gain Privileges
Hide Activities
Modify Data