[ansible/artifactory] JA-7492- Fixed a security issue whereby, interacting with specially c… #356
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.
…rafted URLs could lead to exposure of sensitive information.
PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[ansible/artifactory]
)What this PR does / why we need it:
Below Information is specifically for the Artifactory Version 7.59.9 and above:
The security of your data is the highest priority for JFrog. As such, and in the spirit of open communication, we are writing to inform you of a newly-discovered security vulnerability that affects JFrog Artifactory.
Description
Due to this vulnerability, in some circumstances, user interaction with specially-crafted URLs could lead to data exposure unless corrective action is taken.
For JFrog Self-hosted installations
Versions affected
JFrog Artifactory versions 7.59 and above.
Remediation
The JFrog team has taken immediate action and released fixes for the affected JFrog Artifactory self-hosted versions with the following patches:
7.59.18, 7.63.18, 7.68.19, 7.71.8
JIRA Issue: JA-7492- Fixed a security issue whereby, interacting with specially crafted URLs could lead to exposure of sensitive information.
To fix this issue, you must upgrade your version of JFrog Artifactory to one of the remediating versions.
This PR also includes a fix for #357
Special notes for your reviewer:
Anuraj Nair is in on this one.