ZeroDay Findings
Sign inSign up

Every 4 hours

Cyber

Original briefings from the security press, rewritten for operators. Each story keeps the date of the report it is based on, links the identifiers it discusses, and points back to the original publication.

Threat intelligence

Trackers and reporting desks followed on the same four-hour update. New public reports are rewritten into the briefings below.

PrioritySourceWebsiteInformation
Ransomware.liveWebsiteRansomware.liveInformationRansomware groups, victims, incidents
The DFIR ReportWebsiteThe DFIR ReportInformationDetailed intrusion investigations
SANS Internet Storm CenterWebsiteSANS ISCInformationAttack observations and incident analysis
abuse.ch ThreatFoxWebsiteThreatFoxInformationIndicators of compromise
abuse.ch URLhausWebsiteURLhausInformationMalware distribution infrastructure
abuse.ch MalwareBazaarWebsiteMalwareBazaarInformationMalware hashes and metadata
abuse.ch Feodo TrackerWebsiteFeodo TrackerInformationBotnet command-and-control infrastructure
AlienVault OTXWebsiteAlienVault OTXInformationCommunity threat-intelligence indicators
PhishTankWebsitePhishTankInformationPhishing intelligence
Shadowserver FoundationWebsiteShadowserverInformationInternet exposure and threat reporting

  1. Oct 16, 2024 · ZeroDay Catalog

    Critical Vulnerability in GF(2^m) Elliptic Curve APIs

    A significant vulnerability has been identified in the low-level GF(2^m) elliptic curve APIs, potentially leading to severe memory issues and remote code execution.

    What changed

    Recent findings have highlighted a vulnerability in the low-level GF(2^m) elliptic curve APIs. The use of untrusted explicit values for the field polynomial can result in out-of-bounds memory reads or writes.

    This issue poses a risk of application crashes and could potentially allow for remote code execution under certain conditions.

    Who is affected

    This vulnerability primarily affects applications and systems utilizing elliptic curve cryptography, particularly those that implement the GF(2^m) APIs.

    Organizations relying on cryptographic libraries that expose these APIs may be at risk, especially if they allow untrusted input for curve parameters.

    • Developers using cryptographic libraries that implement GF(2^m) elliptic curves.
    • Organizations that have integrated elliptic curve cryptography into their security protocols.
    • Software vendors that provide cryptographic solutions based on GF(2^m) elliptic curves.

    What to do

    It is crucial for organizations to review their use of elliptic curve APIs and ensure that only trusted values are utilized for field polynomials.

    Implementing strict input validation and adhering to best practices for cryptographic implementations can mitigate the risks associated with this vulnerability.

    • Audit existing applications for the use of GF(2^m) elliptic curve APIs.
    • Ensure that only named curves are used or that explicit parameters are properly validated.
    • Stay informed on updates from cryptographic library vendors regarding patches or mitigations.

    Original report