aiootp 0.13.0 vulnerabilities

Known vulnerabilities in the aiootp package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
H Insufficient Entropy aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library. Affected versions of this package are vulnerable to Insufficient Entropy such that the top-level '(a)csprng' functions were found to be unsafe in concurrent code, leading to the possibility of producing identical outputs from distinct calls if run in quick succession from concurrently running threads & co-routines. Note: This vulnerability does not effect users of the library which are not running it in multiple concurrent threads or co-routines. How to fix Insufficient Entropy? Upgrade `aiootp` to version 0.22.0 or higher.	[,0.22.0)
M Cryptographic Issues aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library. Affected versions of this package are vulnerable to Cryptographic Issues. The new StreamHMAC class ensures the user must contend with ciphertext validation even when using the `_encipher`, `_decipher` & `_xor` Comprende generators. All usages of the `generics.py` hmac functions are impacted by a reordering of the key & argument within those functions to more closely mirror the reasoning behind the HMAC spec. The main `a/_keys` generators used by the pseudo one time pad cipher has been altered to patch a flaw in its design described in `CHANGES.rst`. The database classes filenames have switched from a base36 encoding to base38. How to fix Cryptographic Issues? Upgrade `aiootp` to version 0.18.0 or higher.	[,0.18.0)
M Cryptographic Issues aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library. Affected versions of this package are vulnerable to Cryptographic Issues. If an adversary can get a user to reveal the value returned by the `hmac` method when fed the tag file's filename & the salt used for that encrypted tag, then they could deduce the decryption key for the tag. This version check is here only for backwards compatibility & will be removed on the next update. How to fix Cryptographic Issues? Upgrade `aiootp` to version 0.18.1 or higher.	[,0.18.1)
M Cryptographic Issues aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library. Affected versions of this package are vulnerable to Cryptographic Issues. The HMAC verifiers on ciphertexts did not include the `salt` or `pid` values when deriving the HMAC. This associated data can therefore be changed to cause a party to decrypt a past ciphertext with a salt or pid of an attacker's choosing. How to fix Cryptographic Issues? Upgrade `aiootp` to version 0.17.0 or higher.	[,0.17.0)

Vulnerability

Vulnerable Version

Insufficient Entropy

aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library.

Affected versions of this package are vulnerable to Insufficient Entropy such that the top-level '(a)csprng' functions were found to be unsafe in concurrent code, leading to the possibility of producing identical outputs from distinct calls if run in quick succession from concurrently running threads & co-routines.

Note: This vulnerability does not effect users of the library which are not running it in multiple concurrent threads or co-routines.

How to fix Insufficient Entropy?

Upgrade aiootp to version 0.22.0 or higher.

[,0.22.0)

Cryptographic Issues

aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library.

Affected versions of this package are vulnerable to Cryptographic Issues. The new StreamHMAC class ensures the user must contend with ciphertext validation even when using the *_encipher, *_decipher & *_xor Comprende generators. All usages of the generics.py hmac functions are impacted by a reordering of the key & argument within those functions to more closely mirror the reasoning behind the HMAC spec. The main a/*_keys generators used by the pseudo one time pad cipher has been altered to patch a flaw in its design described in CHANGES.rst. The database classes filenames have switched from a base36 encoding to base38.

How to fix Cryptographic Issues?

Upgrade aiootp to version 0.18.0 or higher.

[,0.18.0)

Cryptographic Issues

aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library.

Affected versions of this package are vulnerable to Cryptographic Issues. If an adversary can get a user to reveal the value returned by the hmac method when fed the tag file's filename & the salt used for that encrypted tag, then they could deduce the decryption key for the tag. This version check is here only for backwards compatibility & will be removed on the next update.

How to fix Cryptographic Issues?

Upgrade aiootp to version 0.18.1 or higher.

[,0.18.1)

Cryptographic Issues

aiootp is an aiootp - an asynchronous pseudo-one-time-pad based crypto and anonymity library.

Affected versions of this package are vulnerable to Cryptographic Issues. The HMAC verifiers on ciphertexts did not include the salt or pid values when deriving the HMAC. This associated data can therefore be changed to cause a party to decrypt a past ciphertext with a salt or pid of an attacker's choosing.

How to fix Cryptographic Issues?

Upgrade aiootp to version 0.17.0 or higher.

[,0.17.0)

aiootp@0.13.0 vulnerabilities

a high-level async cryptographic anonymity library to scale, simplify, & automate privacy best practices for secure data & identity processing, communication, & storage.

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?