-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
fix: The client IP address may be determined incorrectly in some cases #8369
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
fix: The client IP address may be determined incorrectly in some cases #8369
Conversation
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request!
|
Codecov ReportBase: 94.12% // Head: 94.12% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## release-5.x.x #8369 +/- ##
=================================================
- Coverage 94.12% 94.12% -0.01%
=================================================
Files 182 182
Lines 13785 13779 -6
=================================================
- Hits 12975 12969 -6
Misses 810 810
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
## [5.4.1](5.4.0...5.4.1) (2023-01-31) ### Bug Fixes * The client IP address may be determined incorrectly in some cases; it is now required to set the Parse Server option `trustProxy` accordingly if Parse Server runs behind a proxy server, see the express framework's [trust proxy](https://expressjs.com/en/guide/behind-proxies.html) setting; this fixes a security vulnerability in which the Parse Server option `masterKeyIps` may be circumvented, see [GHSA-vm5r-c87r-pf6x](GHSA-vm5r-c87r-pf6x) ([#8369](#8369)) ([e016d81](e016d81))
🎉 This change has been released in version 5.4.1 |
Fixes security vulnerability GHSA-vm5r-c87r-pf6x.