Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API CORS Header Configuration Potentially Allow Unintented Data Leakage #465

Open
AzharSyedGit opened this issue Oct 12, 2023 · 0 comments
Labels
question Further information is requested

Comments

@AzharSyedGit
Copy link

Hello,

During our security scan, we encountered the domain https://api2.amplitude.com/ using the access-control-allow-origin header and it is set to '*', which will allow requests from any domain to access resources being shared. This can lead to exploits where a malicious actor can request from their domain and receive a response that can contain sensitive information.
Can we have the access-control-allow-origin header with a specific whitelist of allowed domains, instead of allowing any domain?

@AzharSyedGit AzharSyedGit added the question Further information is requested label Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant