Resolves #962 #728 removed decodeEntities and escape calls
#1148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es a different set of characters. Also removed "decodeEntities"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes Issues #728 and #962
Summary
Removed calls to
escapeon routes, because new middleware was added that prevents certain characters from being submitted that could potentially cause XSS.decodeEntitieswas also removed because it also potentially enabled XSS.Important Changes
cve.controller/index.js,cve-id.controller/index.js,org.controller/index.jsescape()org.controller.jsdecodeEntitiesTesting
Steps to manually test updated functionality, if possible
npm run testto run all unit and integration tests