-
Bug
-
Resolution: Fixed
-
Medium
-
7.0.10, 7.1.0, 7.1.2, 7.1.4, 7.1.7, 7.1.9, 7.6.0
-
7
-
27
-
Severity 2 - Major
-
90
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Security information
The Webhooks component of Atlassian Jira before version 7.6.7 and from version 7.7.0 before version 7.11.0 allows remote attackers who are able to observe or otherwise intercept webhook events to learn information about changes in issues that should not be sent because they are not contained within the results of a specified JQL query.
Summary
JQL filter for Webhooks dosn't work correctly when Comment or Worklog related events are fired.
Steps to Reproduce
- Create an webhook as follows
- Comment or log work on an issue in a project aside from the one which is specified with the JQL
Expected Results
The webhook shouldn't be fired.
Actual Results
The webhook was fired.
Notes
When it comes to NOT "Comment" or "Worklog" related events (like creating issue, updating issue),
the JQL filters the events correctly.
- is duplicated by
-
JRASERVER-60721 Webhooks for comments do not respect JQL filter
- Closed
-
JRASERVER-63005 Webhook JQL restriction not working for 'Comment Added' event
- Closed
-
JRASERVER-67663 WebHooks based on "worklog" events do not respect the JQL in place
- Closed
- is related to
-
JRASERVER-66134 Return project key in JSON response for comment and worklog related webhook
- Gathering Interest
-
PSR-79 Loading...
- relates to
-
JRACLOUD-59980 JQL filter for Webhooks doesn't work correctly when "Comment", "Worklog", "Attachment" or "IssueLink" related events are fired
- Closed
-
RAID-785 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...