Skip to content

[Bug] Possible overflow parsing timestamps in oauth JWTs as 32 bit int. #260

Closed
@ante012

Description

@ante012

Hi,

Discovered an issue in parsing timestamps in oauth jwts as 32 bit ints. This causes an overflow if tokens expire in > ~13 years.
That is obviously not a reasonable token validity period but will affect everyone in ~13 years :)

Thanks to Marko on slack for a very quick response. He found the relevant code here https://github.com/strimzi/strimzi-kafka-oauth/blob/main/oauth-common/src/main/java/io/strimzi/kafka/oauth/validator/JWTSignatureValidator.java#L475-L483
I think the same issue exists for parsing iat.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions