Mercedes-Benz Source Code Leaked via mishandled GitHub token

Mercedes-Benz has been reported to have leaked its source code due to a GitHub token leak from an organization employee.

This particular leak was identified during an internet scan from a research team, revealing a GitHub repository holding this information.

This token gave unrestricted and unmonitored access to the entire source code that was hosted on the Internal GitHub Enterprise server, which had sensitive information such as intellectual property and compromised information, including Database Connection Strings, Cloud Access Keys, Blueprints, Design Documents, SSO Passwords, API Keys, and Other Critical internal information.

- Advertisement -

Results if Exploited

According to the reports shared with Cyber Security News, if a threat actor had access to this token, there was a variety of sensitive information that the threat actor could use for various malicious operations.

A threat actor could have utilized this token to retrieve all the sensitive information including API keys, Cloud Access keys, etc., to steal data from Mercedes-Benz.

Further, this information could have also been sold at dark web marketplaces in exchange for bitcoins or any cryptocurrency.

Additionally, there could also be financial consequences that could have happened due to data theft, extortion, backdoor deployment, ransomware deployment, and any malicious activities that could benefit the attacker.

From a company perspective, if these data consisted of any kind of consumer information, GDPR violations could have taken place that could cause millions of dollars in loss.

On the other hand, this also spoils Mercedes-Benz’s reputation, leading to a reduction in customers’ trust followed by a loss of business.

Redhunt Labs report details the incident’s consequences, impact, risk, and other information.