{"id":183943,"date":"2026-10-22T05:40:56","date_gmt":"2026-10-22T03:40:56","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/raskryty-detali-kriticheskih-uyazvimostej-v-php-i-opublikovany-korrektiruyushhie-obnovleniya"},"modified":"2026-10-22T05:41:02","modified_gmt":"2026-10-22T03:41:02","slug":"details-of-critical-php-vulnerabilities-disclosed-and-security-updates-released","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/details-of-critical-php-vulnerabilities-disclosed-and-security-updates-released","title":{"rendered":"Detajet e dob\u00ebsive kritike n\u00eb PHP jan\u00eb zbuluar dhe jan\u00eb publikuar p\u00ebrdit\u00ebsime korrigjuese","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Jan\u00eb publikuar versionet korrigjuese PHP 8.5.12, 8.4.27, 8.3.36 dhe 8.2.35, si dhe patches p\u00ebr deg\u00ebt q\u00eb nuk mb\u00ebshteten m\u00eb PHP 7.4, PHP 8.0 dhe PHP 8.1 (versionet e prekura nga 5.4 deri n\u00eb 7.3 nuk kan\u00eb patches), n\u00eb t\u00eb cilat jan\u00eb korrigjuar dy vulnerabilitete kritike:<\/p>\n
\n
CVE-2026-109618 \u2014 ekzekutimi i kodit n\u00eb distanc\u00eb, i shkaktuar nga shfryt\u00ebzimi i memories s\u00eb lir\u00eb t\u00eb disponueshme p\u00ebr procesin. Menaxheri i munges\u00ebs s\u00eb memories, p\u00ebrmes funksionit longjmp(), mund t\u00eb prek\u00eb interpretorin PHP n\u00eb nj\u00eb gjendje ku jan\u00eb inicializuar vet\u00ebm disa nga strukturat e brendshme q\u00eb lidhen me trajtimin e k\u00ebrkes\u00ebs. M\u00eb von\u00eb, funksioni i p\u00ebrfundimit t\u00eb procesit t\u00eb k\u00ebrkes\u00ebs i referohet k\u00ebtyre strukturave si t\u00eb inicializuara, megjith\u00ebse memoria p\u00ebr to nuk \u00ebsht\u00eb ndar\u00eb.\n
Vektori kryesor i sulmit \u00ebsht\u00eb manipulimi i k\u00ebrkesave multipart p\u00ebr t\u00eb krijuar kushte p\u00ebr p\u00ebrfundimin e memories s\u00eb disponueshme p\u00ebr procesin. P\u00ebr t\u00eb anashkaluar kufirin post_max_size, mund t\u00eb mos p\u00ebrmendet header-i Content-Length dhe t\u00eb d\u00ebrgohen nj\u00eb num\u00ebr i madh HTTP header-ash. Mund t\u00eb kryhen gjithashtu sulme t\u00eb precizuara n\u00eb operacione specifike n\u00eb aplikacionet php, q\u00eb konsumojn\u00eb tep\u00ebr memorie. Prania e nj\u00eb exploiti \u00ebsht\u00eb konfirmuar p\u00ebr mod_php, pasi ai th\u00ebrret funksionin shutdown() edhe n\u00eb rast t\u00eb d\u00ebshtimit. PHP-FPM n\u00eb rast d\u00ebshtimi do t\u00eb p\u00ebrfundoj\u00eb procesin f\u00ebmij\u00eb, \u00e7ka e v\u00ebshtir\u00ebson zhvillimin e sulmit, por teorikisht nuk e p\u00ebrjashton at\u00eb. <\/p>\n
CVE-2026-109619 \u2014 ekzekutimi i kodit n\u00eb distanc\u00eb, i shkaktuar nga referimi n\u00eb memorie pas lirimit t\u00eb saj p\u00ebr shkak t\u00eb pastrimit t\u00eb pap\u00ebrshtatsh\u00ebm t\u00eb statusit global t\u00eb lidhur me nj\u00eb k\u00ebrkes\u00eb t\u00eb caktuar. N\u00eb rast se k\u00ebrkesa nd\u00ebrpritet p\u00ebr shkak t\u00eb nj\u00eb gabimi fatal, skadimit t\u00eb koh\u00ebs ose munges\u00ebs s\u00eb memories, statusi global mund t\u00eb mbetet i pap\u00ebrshtatsh\u00ebm dhe treguesit do t\u00eb mbeten aktiv\u00eb, pavar\u00ebsisht lirimit t\u00eb memories q\u00eb ata referohen. Gjat\u00eb trajtimit t\u00eb k\u00ebrkes\u00ebs tjet\u00ebr n\u00eb t\u00eb nj\u00ebjtin proces, mund t\u00eb ndodh\u00eb referimi p\u00ebrmes treguesit t\u00eb mbetur n\u00eb statusin global t\u00eb vjet\u00ebr.\n
P\u00ebr funksionimin e sistemit, mund t\u00eb p\u00ebrdoret krijimi i kushteve t\u00eb shterimit t\u00eb memories s\u00eb disponueshme gjat\u00eb p\u00ebrpunimit t\u00eb k\u00ebrkesave multipart n\u00eb kodin p\u00ebr tregimin e p\u00ebrparimit t\u00eb ngarkimit (session.upload_progress). N\u00eb k\u00ebt\u00eb rast, si vektori kryesor dhe i konfirmuar i sulmit p\u00ebrmendet menaxheri fatal_error_backtraces n\u00eb PHP 8.5, i cili nuk e rikthen gjendjen e drejtimit pas p\u00ebrfundimit. N\u00eb rastin e par\u00eb, sulmi \u00ebsht\u00eb i mundsh\u00ebm mbi mod_php dhe PHP-FPM, nd\u00ebrsa n\u00eb t\u00eb dytin vet\u00ebm mbi mod_php. Po ashtu, p\u00ebrmendet mund\u00ebsia jo e konfirmuar e zhvillimit t\u00eb nj\u00eb sulmi n\u00eb konfigurime, ku ka drejtime q\u00eb \u00e7ojn\u00eb n\u00eb shfaqjen e paralajm\u00ebrimeve n\u00eb faz\u00ebn e hershme t\u00eb p\u00ebrpunimit t\u00eb k\u00ebrkes\u00ebs (p.sh., paralajm\u00ebrimet p\u00ebr p\u00ebrdorimin e parametrave t\u00eb skaduar).<\/p>\n<\/ul>\n
Shtrohet se bllokimi i plot\u00eb i dob\u00ebsive \u00ebsht\u00eb e mundur vet\u00ebm p\u00ebrmes instalimit t\u00eb p\u00ebrdit\u00ebsimeve. Masat e m\u00ebposhtme lejojn\u00eb uljen e probabilitetit t\u00eb realizimit t\u00eb sulmeve, por nuk e b\u00ebjn\u00eb sistemin plot\u00ebsisht t\u00eb sigurt:<\/p>\n
\n
Caktimi n\u00eb php.ini i parametrit \u00abmemory_limit=-1\u00bb, i cili e v\u00ebshtir\u00ebson mund\u00ebsin\u00eb p\u00ebr nj\u00eb sulmues t\u00eb kontrolloj\u00eb shpenzimin e kufijve t\u00eb memories.\n
Caktimi i parametrin \u00abpost_max_size=8M\u00bb n\u00ebse nuk ka nevoj\u00eb p\u00ebr ngarkimin e skedar\u00ebve t\u00eb m\u00ebdhenj. Vlera e parametrave \u00abupload_max_filesize\u00bb duhet t\u00eb jet\u00eb m\u00eb e vog\u00ebl se e parametrave \u00abpost_max_size\u00bb.\n
Vendosja e nj\u00eb limiti p\u00ebr konsumin e memories n\u00eb nivel sistemor, p\u00ebrmes cgroup memory.max ose parametrave t\u00eb konsumit t\u00eb memories nga kontejneri, por jo p\u00ebrmes limiteve sistemore RLIMIT_AS dhe RLIMIT_DATA, t\u00eb cilat vet\u00ebm provokojn\u00eb thirrjen problematike longjmp().\n
N\u00ebse aktivizimi i performanc\u00ebs nuk \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm, mund t\u00eb kufizohet numri i k\u00ebrkesave q\u00eb nj\u00eb proces punues i trajton p\u00ebrmes pm.max_requests=1 n\u00eb PHP-FPM dhe MaxRequestsPerChild n\u00eb Apache httpd.\n