Secret leaks often occur when a sensitive piece of authentication data is stored with the source code of an application. Considering the source code is intended to be deployed across multiple assets, including source code repositories or application hosting servers, the secrets might get exposed to an unintended audience.
In most cases, trust boundaries are violated when a secret is exposed in a source code repository or an uncontrolled deployment environment. Unintended people who don’t need to know the secret might get access to it. They might then be able to use it to gain unwanted access to associated services or resources.
The trust issue can be more or less severe depending on the people’s role and entitlement.
A Facebook application secret key is a unique authentication token assigned to a Facebook application. It is used to authenticate and authorize the application to access Facebook’s APIs and services. This key is required to perform actions on Facebook API, such as retrieving user data, posting on behalf of users, or accessing various Facebook features.
If a Facebook application secret key leaks to an unintended audience, it can have serious security-related consequences both for the associated Facebook application and its users. Especially, attackers knowing an application’s secret key will be able to access users' data that the application has been granted access to.
This can represent a severe confidentiality loss for Personally Identifiable Information. This might be against national regulatory requirements in some countries.
Revoke the secret
Revoke any leaked secrets and remove them from the application source code.
Before revoking the secret, ensure that no other applications or processes is using it. Other usages of the secret will also be impacted when the secret is revoked.
Use a secret vault
A secret vault should be used to generate and store the new secret. This will ensure the secret’s security and prevent any further unexpected disclosure.
Depending on the development platform and the leaked secret type, multiple solutions are currently available.
props.set("facebook_secret", "a569a8eee3802560e1416edbc4ee119d")
props.set("facebook_secret", System.getenv("FACEBOOK_SECRET"))