Skip to content

CVE-2024-23342 Timing Attack #330

Closed as not planned
kleinbem/actions
#16
Closed as not planned

Description

@yaronbenezra

Hello,

SNYK and other scanning tools alerts on package vulnerability ( Timing Attack ) found at "sign_digest" API function.
( ecdsa.SigningKey.sign_digest() )

https://www.cve.org/CVERecord?id=CVE-2024-23342( HIGH Alert)

Can you address when you are going to fix this?

Regards,
Yaron

Activity

  1. maksimu commented on Jan 24, 2024

    @maksimu

    We are also interesting is the ETA for the fix

  2. added
    bugunintended behaviour in ecdsa code
    on Jan 24, 2024
  3. tomato42 commented on Jan 24, 2024

    @tomato42
    Member

    as stated in the vulnerability release GHSA-wj6h-64fc-37mp and as stated in the security policy timing attacks are outside the scope of the project.

    If you need an implementation that is safe against side-channel attacks, I recommend using https://github.com/pyca/cryptography

    It's a won't fix.

  4. alopezlopez4 commented on Feb 13, 2024

    @alopezlopez4

    Hi @tomato42, can you give more details on what you mean by "timing attacks are outside the scope of the project."? Does it mean that ecdsa is not affected or just that resolving that vulnerability is responsibility of the users of ecdsa? Thanks

  5. tomato42 commented on Feb 13, 2024

    @tomato42
    Member

    @dlpzx I mean that Python doesn't provide the primitives that are side-channel free, so it's impossible to build a side-channel free implementation on top of them. To actually fix it, it would require implementing the whole operation in C, which is a non-goal for the library (as it won't be a pure-python any more)

  6. eshgovil commented on Sep 24, 2025

    @eshgovil

    IMO it doesn't make sense to be ideological about pure-python when it means every end-user that has to meet security requirements (anyone that delivers code for enterprise) will no longer use the library :/

  7. tomato42 commented on Sep 25, 2025

    @tomato42
    Member

    I don't want people to use this library in production environments...

    It's a teaching tool, it's a testing tool, it's absolutely not an production grade implementation.
    I maintain it to have support for ECDH and ECDSA in tlsfuzzer, which I need to be first and foremost portable. Security does not even enter a picture for that tool.

    If you need enterprise grade implementation you should use pyca/cryptography.

  8. added a commit that references this issue on Feb 9, 2026
  9. added a commit that references this issue on Feb 18, 2026
  10. added a commit that references this issue on Feb 23, 2026
  11. added a commit that references this issue on Feb 26, 2026
  12. added a commit that references this issue on Nov 6, 2026
    246758d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugunintended behaviour in ecdsa code

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions