freeipa

Clone
Source Code
GIT

#5333 Negative offset during otptoken-sync suffers causes integer underflow
Closed: Fixed None Opened 8 years ago by tbabej.

Closed: Fixed
Reopen Issue

If a negative offset between the device and the server is detected during otptoken-sync, it will underflow, and set a large positive value as offset instead.

-------------------
1 OTP token matched
-------------------
  dn:
ipatokenuniqueid=1e7a8029-8872-46f5-8254-9d03a62d2417,cn=otp,dc=ipa,dc=test
  Unique ID: 1e7a8029-8872-46f5-8254-9d03a62d2417
  Type: TOTP
  Owner: test
  Key: eu/S8oUunB188tRc5HE8CkxMmyI=
  Algorithm: sha1
  Digits: 6
  Clock offset: 4294963816
  Clock interval: 30
  ipatokentotpwatermark: 48117551
  objectclass: top, ipatokentotp, ipatoken

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1267253

master:

  • d3cca6db57fb26aea1d45bc522336dddc6256825 Fix an integer underflow bug in libotp

ipa-4-2:

  • 3c52f62e6c4e07b107780d95a6a4ff79d89c75b9 Fix an integer underflow bug in libotp

Moving to a proper bucket.

master:

  • 9e3eead Fix an integer underflow bug in libotp

ipa-4-2:

  • 7db0a8e Fix an integer underflow bug in libotp

Hashes in the comment 2 are not correct, hence comment 5.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1217009 (Red Hat Enterprise Linux 7)

Metadata Update from @tbabej:
- Issue assigned to someone
- Issue set to the milestone: FreeIPA 4.2.2
7 years ago

Login to comment on this ticket.

Metadata
None
None
None
normal
None
None
None
None
defect
None
None
IPA
None
0
None
None
None
None
https://bugzilla.redhat.com/show_bug.cgi?id=1267253, https://bugzilla.redhat.com/show_bug.cgi?id=1217009
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.