{"id":182227,"date":"2026-06-18T08:48:05","date_gmt":"2026-06-18T06:48:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/obnovlenie-nginx-1-31-2-s-ustraneniem-uyazvimostej-ekspluatiruemyh-cherez-http-3-http2-i-grpc"},"modified":"2026-06-18T08:48:05","modified_gmt":"2026-06-18T06:48:05","slug":"obnovlenie-nginx-1-31-2-s-ustraneniem-uyazvimostej-ekspluatiruemyh-cherez-http-3-http2-i-grpc","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/news\/obnovlenie-nginx-1-31-2-s-ustraneniem-uyazvimostej-ekspluatiruemyh-cherez-http-3-http2-i-grpc","title":{"rendered":"Aktualizace nginx 1.31.2 s odstran\u011bn\u00edm zranitelnost\u00ed vyu\u017e\u00edvan\u00fdch p\u0159es HTTP\/3, HTTP2 a gRPC","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Byl vyd\u00e1n hlavn\u00ed vyd\u00e1n\u00ed nginx 1.31.2, v r\u00e1mci kter\u00e9ho pokra\u010duje rozvoj nov\u00fdch mo\u017enost\u00ed, a tak\u00e9 bylo vyd\u00e1no paraleln\u011b podporovan\u00e9 stabiln\u00ed vyd\u00e1n\u00ed nginx 1.30.3, do kter\u00e9ho jsou prov\u00e1d\u011bny pouze zm\u011bny souvisej\u00edc\u00ed s opravou z\u00e1va\u017en\u00fdch chyb a zranitelnost\u00ed. V aktualizac\u00edch bylo odstran\u011bno 3 zranitelnosti:<\/p>\n
\n
CVE-2026-42530 \u2014 p\u0159\u00edstup k ji\u017e uvoln\u011bn\u00e9 pam\u011bti (use-after-free) v implementaci protokolu HTTP\/3. Probl\u00e9m byl ohodnocen kritick\u00fdm stupn\u011bm nebezpe\u010d\u00ed (9,2 z 10), co\u017e m\u016f\u017ee umo\u017enit vzd\u00e1len\u00e9 spu\u0161t\u011bn\u00ed k\u00f3du s pr\u00e1vy pracovn\u00edho procesu p\u0159i zpracov\u00e1n\u00ed speci\u00e1ln\u011b form\u00e1tovan\u00e9 relace podle protokolu QUIC.\n
CVE-2026-42055 \u2014 p\u0159ete\u010den\u00ed vyrovn\u00e1vac\u00ed pam\u011bti v modulech ngx_http_proxy_v2_module a ngx_http_grpc_module, kter\u00e9 se projevuje p\u0159i proxyov\u00e1n\u00ed speci\u00e1ln\u011b form\u00e1tovan\u00fdch po\u017eadavk\u016f podle protokolu HTTP\/2 nebo k backendu gRPC. Probl\u00e9m byl ohodnocen kritick\u00fdm stupn\u011bm nebezpe\u010d\u00ed (9,2 z 10), co\u017e umo\u017e\u0148uje vzd\u00e1len\u00e9 spu\u0161t\u011bn\u00ed k\u00f3du. Zranitelnost se objevuje v konfigurac\u00edch s nastaven\u00edm \n\u201eignore_invalid_headers off;\u201c a velkou hodnotou \u201elarge_client_header_buffers.\u201c<\/p>\n
CVE-2026-48142 \u2014 \u010dten\u00ed z oblasti mimo p\u0159id\u011blen\u00fd buffer p\u0159i zpracov\u00e1n\u00ed speci\u00e1ln\u011b form\u00e1tovan\u00fdch po\u017eadavk\u016f, co\u017e vede k p\u0159ek\u00f3dov\u00e1n\u00ed textu v k\u00f3dov\u00e1n\u00ed UTF-8 pomoc\u00ed modulu ngx_http_charset_module. Zranitelnost se objevuje v konfigurac\u00edch s direktivou \u201echarset_map\u201c p\u0159i p\u0159\u00edtomnosti v bloku location direktiv \u201esource_charset utf-8\u201c a \u201echarset jin\u00e1_k\u00f3dov\u00e1n\u00ed.\u201c Probl\u00e9m byl ohodnocen st\u0159edn\u00edm stupn\u011bm nebezpe\u010d\u00ed (6,3 z 10), co\u017e umo\u017e\u0148uje \u00fanik obsahu pam\u011bti pracovn\u00edho procesu.\n<\/ul>\n
Krom\u011b opravy zranitelnost\u00ed ve verzi nginx 1.31.2 byla p\u0159id\u00e1na prom\u011bnn\u00e1 $ssl_sigalgs, obsahuj\u00edc\u00ed algoritmy digit\u00e1ln\u00edch podpis\u016f deklarovan\u00e9 klientem ve zpr\u00e1v\u011b ClientHello b\u011bhem vyjedn\u00e1v\u00e1n\u00ed TLS spojen\u00ed. Pro tvorbu identifik\u00e1toru, kter\u00fd je p\u0159en\u00e1\u0161en prost\u0159ednictv\u00edm prom\u011bnn\u00e9 $request_id, byl vyu\u017eit hashovac\u00ed algoritmus SipHash-2-4. \n Zdroj: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"