Weaknesses of type CWE-130

106 results

Inconsistência no tratamento de parâmetros de comprimento

Ocorre quando o código não valida ou trata adequadamente inconsistências entre o comprimento declarado de um buffer/string e seu tamanho real. Um atacante explora essa discrepância para causar leitura ou escrita fora dos limites, levando a vazamento de dados, corrupção de memória ou execução de código.

Example

Uma função recebe uma string com um parâmetro 'length' que não corresponde ao tamanho real do buffer. Se o código copia 'length' bytes sem verificar se o buffer realmente possui esse tamanho, um memcpy() ou strcpy() escreve além do limite alocado, ou lê dados inválidos de memória adjacente.

How to mitigate

Sempre validar que o parâmetro de comprimento é coerente com o tamanho real do buffer antes de operações de cópia ou leitura. Use funções seguras (strncpy, memcpy_s) e implemente checks explícitos: se length > buffer_size, rejeitar ou truncar. Ferramentas de análise estática ajudam a detectar esse padrão.

CVE-2024-53856HIGHrPGP Panics on Malformed Untrusted InputEPSS 0.4%CVE-2024-37305HIGHBuffer overflow in deserialization in oqs-provider EPSS 0.4%CVE-2022-41586HIGHThe communication framework module has a vulnerability of not truncating data properly.Successful exploitation of this vulnerability may affEPSS 0.4%CVE-2026-43125CRITICALdlm: validate length in dlm_search_rsb_treeEPSS 0.4%CVE-2026-5766MEDIUMPotential denial-of-service vulnerability in ASGI requests via file upload limit bypassEPSS 0.4%CVE-2025-29931MEDIUMA vulnerability has been identified in TeleControl Server Basic (All versions < V3.1.2.2). The affected product does not properly validate aEPSS 0.4%CVE-2025-30659HIGHJunos OS: SRX Series: A device configured for vector routing crashes when receiving malformed trafficEPSS 0.4%CVE-2026-41035HIGHIn rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. TEPSS 0.4%CVE-2025-32366MEDIUMIn ConnMan through 1.44, parse_rr in dnsproxy.c has a memcpy length that depends on an RR RDLENGTH value, i.e., *rdlen=ntohs(rr->rdlen) and EPSS 0.4%CVE-2026-3868HIGHAn improper handling of the length parameter inconsistency vulnerability has been identified in Moxa’s Secure Router. Because of improper vaEPSS 0.4%CVE-2026-22255HIGHiccDEV has heap-buffer-overflow in CIccCLUT::Init() at IccProfLib/IccTagLut.cppEPSS 0.4%CVE-2026-26081MEDIUMHAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise and ALOHA are also EPSS 0.4%CVE-2026-4371HIGHOut of bounds read in IMAP parsingEPSS 0.4%CVE-2025-53604MEDIUMThe web-push crate before 0.10.3 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a CEPSS 0.3%CVE-2026-22047HIGHiccDEV has heap-buffer-overflow in SIccCalcOp::Describe() at IccProfLib/IccMpeCalc.cppEPSS 0.3%CVE-2026-35547HIGHHeap overflow in libnvEPSS 0.3%CVE-2026-6432MEDIUMImproper bounds validation in EmberZNet SDKEPSS 0.3%CVE-2026-40199MEDIUMNet::CIDR::Lite versions before 0.23 for Perl mishandles IPv4 mapped IPv6 addresses, which may allow IP ACL bypassEPSS 0.3%CVE-2024-35313HIGHIn Tor Arti before 1.2.3, circuits sometimes incorrectly have a length of 3 (with full vanguards), aka TROVE-2024-004.EPSS 0.3%CVE-2026-33555MEDIUMAn issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches a previously announcEPSS 0.3%