SAST finding is duplicated with an entry that is completely different

Summary

I have a new SAST finding that's somehow merged with a different one from the history that happens to have been dismissed. Because of that, the scan result policy isn't applied (because the finding isn't new). See !95627 (closed) and the vulnerability in the MR widget.

This finding

image

was duplicated with

image

Steps to reproduce

I don't know the conditions to reproduce unfortunately, but see above for a reference to a real case.

Example Project

See MR link in the summary

What is the current bug behavior?

Different vulnerabilities are considered duplicates

What is the expected correct behavior?

Different vulnerabilities should be considered unique and have separate entries in the report

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes