The signing key that is being set, is _not_ what is being parsed.
A _JWT_ is being parsed, that will then be verified using the set key.
(Or in our case not, because we're looking for security problems :P)
This commit is contained in:
intrigus-lgtm 2023-09-04 01:54:06 +02:00
Родитель b291ee361a
Коммит b6417ca212
1 изменённых файлов: 1 добавлений и 1 удалений

Просмотреть файл

@ -16,5 +16,5 @@ import MissingJwtSignatureCheckFlow::PathGraph
from MissingJwtSignatureCheckFlow::PathNode source, MissingJwtSignatureCheckFlow::PathNode sink
where MissingJwtSignatureCheckFlow::flowPath(source, sink)
select sink.getNode(), source, sink, "This parses a $@, but the signature is not verified.",
select sink.getNode(), source, sink, "This sets a $@, but the signature is not verified.",
source.getNode(), "JWT signing key"