chore(deps): update dependency parse [security] #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.11.0
->^1.11.0 || ^5.0.0
1.11.0
->2.10.0
GitHub Vulnerability Alerts
GHSA-wvh7-5p38-2qfc
The
setPassword
method (http://parseplatform.org/Parse-SDK-JS/api/2.9.1/Parse.User.html#setPassword) stores the user's password in localStorage as raw text making it vulnerable to anyone with access to your localStorage. We believe this is the only time that password is stored at all. In the documentation under Users > Signing Up, it clearly states, "We never store passwords in plaintext, nor will we ever transmit passwords back to the client in plaintext."Example Code:
After running the above code, the new password will be stored in localStorage as a property named "password".
Proposed Solution:
Before saving anything to localStorage, Parse should strip out any properties named "password" that are attempting to be stored with a Parse.User type object.
Configuration:
Parse SDK: 2.9.1
Parse Server: 3.9.0
Release Notes
parse-community/Parse-SDK-JS (parse)
v5.3.0
Compare Source
Bug Fixes
Parse.Object.get
returns array instead of object if key name is number-like (#2201) (5921ba2)Features
v5.2.0
Compare Source
Bug Fixes
LiveQueryClient.resubscribe
with Parse Server 7 causes many open connections (#2184) (71b4d17)Parse.Installation
not working when installation is deleted on server (#2126) (22360b4)PushStatus
offset fields (#2194) (e0eb6f0)Features
v5.1.0
Compare Source
Bug Fixes
Parse.GeoPoint.current
returnsundefined
(#2127) (3860535)access-control-expose-headers
when calling Cloud Function (#2095) (7b73c03)Parse.Query.notEqualTo
is set tonull
(#2102) (6afd32a)ParseObject.toJSON()
to return incorrect object (#1453) (23cc573)Features
Parse.User.verifyPassword
using master key and optionignoreEmailVerification: true
(#2076) (b0adf7e)Parse.ACL
from json (#2097) (72bc9ac)Parse.EventuallyQueue
(#2106) (f92e4d4)Parse.Installation.currentInstallation
to support web push notifications (#2119) (4fc62ce)Parse.CoreManager
controllers to add support for swappableCryptoController
,LocalDatastoreController
,StorageController
,WebSocketController
,ParseLiveQuery
(#2100) (fbd0ab1)v5.0.0
Compare Source
Bug Fixes
Parse.Object.relation.add
multiple times adds only the first object (#2078) (0f98117)Features
Parse.Query.comment
(#2088) (a970913)BREAKING CHANGES
v4.3.1
Compare Source
Bug Fixes
Parse.Object.saveEventually
andParse.Object.destroyEventually
not handled on customParse.Error.CONNECTION_FAILURE
message (#2032) (4da3ebc)Cannot find module 'taffydb'
(#2036) (dc91d0f)window.indexedDB
API is available but protected (#2039) (360981f)v4.3.0
Compare Source
Bug Fixes
ParseUser.linkWith
doesn't remove anonymous auth data (#2007) (7e2585c)react-native
path does not work for workspace builds (#1930) (8222f3c)Features
Parse.Schema
(#2001) (343d0d7)ParseUser.logIn
(#2010) (2446007)ParseQuery.findAll
(#2000) (012ba4c)installationId
viaParse.Cloud.run
(#1939) (eb70b93)Parse.Error
message with custom message via new Core Manager optionPARSE_ERRORS
(#2014) (be0c8a6)ParseUser.logInWithAdditionalAuth
(#1955) (2bad411)v4.2.0
Compare Source
Bug Fixes
Parse.File.cancel
starts new attempt to save file (#1781) (b755e42)Features
Parse.User.loginAs
(#1875) (381fcfc)ParseQuery.watch
to trigger LiveQuery only on update of specific fields (#1839) (7479343)v4.1.0
Compare Source
Bug Fixes
LiveQuerySubscription.unsubscribe
resolves promise before unsubscribing completes (#1727) (1c96205)Parse.Object
with an unsavedParse.File
fails (#1662) (16535a4)Features
LiveQueryClient.close
returns promise when WebSocket closes (#1735) (979d660)package-lock.json
to version 2 (#1729) (e993786)v4.0.1
Compare Source
Bug Fixes
containedIn
not working when field is an array (#1666) (2391bff)Parse.Object.extend
(#1682) (f555c43)v4.0.0
Compare Source
Bug Fixes
Parse.Query.subscribe()
does not return a rejected promise on error in Cloud Code TriggersbeforeConnect
orbeforeSubscribe
(#1490) (96d7174)Features
Performance Improvements
BREAKING CHANGES
Parse.Query.subscribe()
will now return a rejected promise if an error is thrown in Cloud Code TriggersbeforeConnect
orbeforeSubscribe
; in previous releases a resolved promise was returned, even if subscribing failed and it was necessary to create anerror.on
listener to handle these errors (#1490) (96d7174)v3.5.1
Compare Source
Bug Fixes
v3.5.0
Compare Source
Warning
Bug Fixes
Parse.User.signUp()
does not pass context to Cloud Code (#1527) (53edcfd)Schema.addField
does not correctly add value of typeDate
(#1544) (15111f7)indexedDB
(#1569) (3560a5e)Features
json
option toParse.Query.each()
(#1539) (89fd5ec)Parse.Object.objectId
automatically whenallowCustomObjectId
is enabled and noobjectId
is passed (#1540) (68f3ff5)v3.4.4
Compare Source
Bug Fixes
ParseQuery.select
overrides properties (#1488) (b80eee4)v3.4.3
Compare Source
Bug Fixes
Parse.File
with base64 string fails for some file types (#1467) (c07d6c9)Parse.Role
throws incorrect error (#1481) (8326a6f)v3.4.2
Compare Source
Bug Fixes
v3.4.1
Compare Source
Bug Fixes
v3.4.0
Compare Source
Bug Fixes
Features
v3.3.1
Compare Source
3.3.1
Full Changelog
Fixes
v3.3.0
Compare Source
Improvements
Fixes
v3.2.0
Compare Source
Breaking Changes
See https://community.parseplatform.org/t/anonymous-user-destroyed-on-logout/1425
Improvements
Parse.Object.registerSubclass
(#1315)Fixes
v3.1.0
Compare Source
Breaking Changes
Parse.Push.send
will now return the pushStatusId instead of{ result: true }
Features
Parse.getServerHealth()
(#1307)Parse.allowCustomObjectId = true
(#1309)Parse.Push.send
now returns pushStatusId (#1302)Parse.Push.getPushStatus
(#1302)Improvements
query.startsWith
(#1306)query.endsWith
(#1306)Fixes
/health
endpoint, caused 403 forbidden side effect (#1305)v3.0.0
Compare Source
Breaking Changes
For security purposes, logIn will default to
POST
instead ofGET
method. (#1284)If you need to use
GET
set theusePost
option to false.Parse.User.logIn('username', 'password', { usePost: false })
Features
{ json: true }
on queries (#1294)Improvements
Fixes
Date
(#1293)v2.19.0
Compare Source
Features
Improvements
Fixes
v2.18.0
Compare Source
Features
Improvements
Fixes
v2.17.0
Compare Source
Improvements
v2.16.0
Compare Source
Idempotency enforcement for client requests. This deduplicates requests where the client intends to send one request to Parse Server but due to network issues the server receives the request multiple times.
(Parse-Server 4.3.0+)
Caution, this is an experimental feature that may not be appropriate for production.
To enable use either of the following:
Parse.CoreManager.set('IDEMPOTENCY', true)
Parse.idempotency = true
Features
Improvements
Fixes
v2.15.0
Compare Source
Features
Fixes
v2.14.0
Compare Source
New Features
Improvements
Fixes
v2.13.0
Compare Source
New Features
Improvements
Fixes
v2.12.0
Compare Source
New Features
Improvements
Fixes
v2.11.0
Compare Source
New Features
Improvements
Fixes
v2.10.0
Compare Source
New Features
Fixes
Parse.Object.registerSubclass('_User', CustomUser);
Security
v2.9.1
Compare Source
Fixes
v2.9.0
Compare Source
Deprecation
_linkWith
and_logInWith
are deprecated. Replace withlinkWith
andlogInWith
respectively. (#963)New Features
Fixes
Improvements
v2.8.0
Compare Source
New Features
Fixes
Improvements
v2.7.1
Compare Source
New Features
ParseConfig.save
withmasterKeyOnlyFlags
option (#910) (Requires Parse-Server 3.8.0+)ParseConfig.get
withuseMasterKey
option (#907)v2.7.0
Compare Source
New Features
ParseObject.fetchAllIfNeededWithInclude
(#900)ParseObject.exists
(#898)ParseObject.save
withcascadeSave
option (#881)Fixes
ParseUser.become
should return subclass (#897)Improvements
@babel/polyfill
(#877)v2.6.0
Compare Source
New Features:
- Support configurable WebSocketController (#64f359a)
- Support for WeChat Mini Program (#874)
- Support withCount query constraint (#868)
Improvements:
- Fix SERVER_RENDERING environment variable (#873)
v2.5.1
Compare Source
v2.4.0
Compare Source
New Features:
Improvements:
Dependency Updates:
Development Dependency Updates:
v2.3.2
Compare Source
Improvements:
getData
from Parse.File (#780)logIn
andlink
support MasterKey and SessionToken options (#779)Fixes:
http
andhttps
from React-Native build (#776)v2.3.1
Compare Source
Improvements:
_linkWith
and_unlinkFrom
support MasterKey and SessionToken options (#767)Fixes:
Miscellaneous:
v2.3.0
Compare Source
Breaking Changes:
query.subscribe()
andunsubscribe()
returns Promise.Improvements:
v2.2.1
Compare Source
Fixes:
v2.2.0
Compare Source
v2.1.0
Compare Source
v2.0.2
: 2.0.2Compare Source
2.0.2
v2.0.1
Compare Source
v2.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.