CVE-2021-24115

In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and hex)

published February 22, 2021

CVSS
—
EPSS
2%
Percentile
79.8
In the wild
Unconfirmed
What it is

⚠️ Yikes! Some encoding ops in Botan before 2.17.3 don’t use constant-time methods—think of it as a bridge that can creak under the wrong weight! Imagine a restaurant where every order is prepared with a different speed based on who’s watching. Some dishes take longer when a critic is present, making the whole process unpredictable. Similarly, these encoding operations might leak timing information, revealing sensitive data to an attacker who’s paying attention. If an attacker can time their request just right, they may exploit the inconsistencies in these operations, potentially gleaning sensitive information before you even notice something's off. While this isn't a direct path to compromise, it's a surprisingly sneaky way to gather intelligence that could lead to larger issues down the line.

Put simply

Imagine a restaurant where every order is prepared with a different speed based on who’s watching. Some dishes take longer when a critic is present, making the whole process unpredictable. Similarly, these encoding operations might leak timing information, revealing sensitive data to an attacker who’s paying attention. This vulnerability stems from the lack of constant-time implementations for certain encoding and decoding operations (base32, base58, base64, and hex) in Botan versions prior to 2.17.3, allowing attackers to potentially perform timing attacks.

What to do

If an attacker can time their request just right, they may exploit the inconsistencies in these operations, potentially gleaning sensitive information before you even notice something's off. While this isn't a direct path to compromise, it's a surprisingly sneaky way to gather intelligence that could lead to larger issues down the line. Upgrade Botan to version 2.17.3 or later immediately to seal off this issue. If you're still using earlier versions, it’s time to assess your encoding needs and implement secure coding practices for critical data. 🛡️ You’ve got this! With a simple upgrade, you’ll fortify your defenses against these pesky timing attacks! 💪✨

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01922 · 79.8th percentile
Published
2021-02-22T01:57Z
EPSS history
Timeline
  • 22 FEB 01:57Z
    In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and hex)
    cvelistv5