CVE-2026-30910
HighSummary
Wersje Crypt::Sodium::XS do 0.001000 dla Perla mają potencjalne przepełnienia całkowite. Funkcje szyfrowania, tworzenia podpisów oraz bin2hex nie sprawdzają, czy rozmiar wyjścia będzie mniejszy niż SIZE_MAX, co może prowadzić do przepełnienia całkowitego i zbyt małego bufora wyjściowego.
Risk Assessment
Może to prowadzić do awarii w funkcji bin2hex oraz algorytmach szyfrowania innych niż aes256gcm. W przypadku szyfrowania aes256gcm i podpisów, zbyt mały bufor może skutkować przepełnieniem bufora.
Recommendation
Zaleca się monitorowanie długości wiadomości oraz aktualizację do nowszej wersji Crypt::Sodium::XS, aby uniknąć potencjalnych problemów z bezpieczeństwem.
Related vulnerabilities
- CVE-2026-86106Critical
An unauthenticated actor with network access to the private HA interconnect may trigger sensitive HA peer functions without verification. This could result in elevated command execution on Edge units where HA is enabled.
- CVE-2026-73453Critical
An unauthenticated P4Runtime client can achieve arbitrary code execution under certain conditions on affected platforms running Arista EOS configured with P4Runtime. By crafting a malicious packet during session initiation, an attacker can obtain complete administrative control over the switch.
- CVE-2026-81642Critical
In NLnet Labs Unbound up to and including 1.26.0, a vulnerability in the DNSSEC validator enables denial of service and possible remote code execution via DNSKEY processing. A crafted DNSKEY can overflow the digest buffer.
- CVE-2026-27565Critical
An unauthenticated remote attacker can upload a malicious IODD file that places and executes a shell script with root privileges. The script remains active even after a reboot.
- CVE-2026-27546Critical
An unauthenticated remote attacker can exploit an authentication bypass in the _account_log function to log in as an admin, even when accounts are properly configured.
- CVE-2026-73447Critical
A privileged attacker can exploit gNSI Certz service on Arista EOS-based products to escalate privileges and execute arbitrary OS commands via a crafted Certz Rotate request. The Bootz service is also affected.
- CVE-2026-14349Critical
The TrueBooker – Appointment Booking and Scheduler System plugin for WordPress in all versions up to and including 1.2.3 is vulnerable to authorization bypass. This is due to the plugin not properly verifying that a user is authorized to perform an action. This allows unauthenticated attackers to modify the email address of arbitrary user accounts, including administrators, which can be leveraged to reset the account password and gain access.
- CVE-2026-12793Critical
The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress in all versions up to and including 3.6.2 is vulnerable to Privilege Escalation. This is due to the plugin not validating that a submitted form ID belongs to a JetFormBuilder form before parsing the referenced post's content as form schema and executing an Advanced Validation server-side callback. This allows unauthenticated attackers to create a new administrator-level user account.
- CVE-2026-15640Critical
Under certain conditions a valid SAML IdP response may be used to impersonate another Secret Server user. The vulnerability affects the SAML authentication mechanism.
- CVE-2026-15639Critical
An attacker can craft a malicious link that, if used by a legitimate user, may cause the user's browser to run JavaScript supplied by the attacker. The vulnerability affects the link processing mechanism.
Original NVD description (English source)
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow. Encountering this issue is unlikely as the message length would need to be very large. For bin2hex the input size would have to be > SIZE_MAX / 2 For aegis encryption the input size would need to be > SIZE_MAX - 32U For other encryption the input size would need to be > SIZE_MAX - 16U For signatures the input size would need to be > SIZE_MAX - 64U

