Аналитика Telegram-канала
Подписчики
2 935
Охват за 24 ч
113
ER за 24 ч
3,85%
Публикаций
680
Динамика подписчиков
7 дней
30 дней
6 месяцев
Больше
13 ноя16 ноя19 ноя
Показаны последние 7 дней
Больше истории →
Охваты публикаций
28.1031.1010.1112.1114.1114.11
23
Средний охват
42
Лучший результат
Показаны 6 публикаций — последние в канале
Больше статистики →
Упоминания
105
Упоминаний
66
Из них репостов
8
Каналов
0
Упоминаний за 90 дней
0
Из них репостов
0
Каналов за 90 дней
Последние посты
3 из 680 2 из 680
About Remote Code Execution - GitLab (CVE-2026-110264) vulnerability. GitLab is a platform for hosting code, collaborative software development, project management, and automating application testing and releases. GitLab CE is the free, open-source version of the platform, while GitLab EE is the enterprise version with additional features. Under certain conditions, the vulnerability in GitLab CE/EE allows an unauthenticated attacker to execute arbitrary code on the server. The vulnerability existed in GitLab for approximately 12 years and affected GitLab CE/EE versions 7.0 and later.
The vulnerability is caused by the following issue. GitLab uses the Ruby programming language to implement a significant part of its server-side logic. In particular, the platform's backend is built on Ruby on Rails, a web framework written in Ruby. Ruby also uses additional libraries and built-in components to perform various tasks. One of these is Onigmo, a regular expression engine responsible for searching and processing text based on predefined patterns. According to Censys research, the vulnerability is related to the processing of Org mode files with the .org extension. When converting these files to HTML, GitLab uses the org-ruby library, which processes user-defined keywords in documents, such as #+TODO:. An attacker can provide a specially crafted value for such a keyword, triggering an overflow in the Onigmo regular expression engine, resulting in memory corruption. Under certain conditions, this can lead to arbitrary code execution on the GitLab server. To exploit the vulnerability, an attacker needs to upload a specially crafted file to a public project. For example, if self-registration is enabled and users are allowed to create public projects, an attacker can register an account and create their own project. Once the file is uploaded, the vulnerable handler can be triggered simply by opening the file's preview page without authentication.
A compromised GitLab server may give an attacker access to project source code, access tokens, credentials, and other sensitive information. After gaining control of the server, an attacker may modify source code or build processes to inject malicious code into distributed applications. In addition, a compromised GitLab server can serve as a starting point for further attacks against the organization's internal infrastructure.
⚙️ The vulnerability has been fixed in versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, and 18.11.13. Infrastructure managed by GitLab itself, including GitLab.com and GitLab Dedicated, is already protected against this vulnerability. If GitLab was installed from unofficial packages and uses a custom Ruby version, updating GitLab alone is not sufficient. This applies, for example, to custom-built GitLab versions and installations using custom container images. In such cases, Ruby must also be updated separately to version 3.3.13, 3.4.12, or 4.0.9 or later. This is because the fix for CVE-2026-110264 was implemented directly in Ruby, not in the GitLab code. The fix is already included in the official GitLab Linux packages and container images.
The GitLab security team has released two detection rules to identify potential attacks against self-hosted GitLab instances: Onigmo native worker crash and Org mode render error burst.
🛠 PoC exploits have been available on GitHub since October 22.
👾 There is currently no evidence that the vulnerability has been exploited in the wild.
🌐 According to Shadowserver, more than 10,000 vulnerable GitLab instances are exposed to the Internet.
@avleonovcom #GitLab #Ruby #RubyOnRails #Censys #Shadowserver #opensource #Onigmo #OrgRuby #DevSecOps #GitHub
ещё
10
2
3 14 ноя, 03:02
About Remote Code Execution - PHP "PHP2Shell" (CVE-2026-109618, CVE-2026-109619) vulnerabilities. PHP is a popular server-side programming language. The vulnerabilities, covered in the October Linux Patch Wednesday, allow unauthenticated remote code execution through specially crafted requests. CVE-2026-109618 is caused by improper OOM error handling, while CVE-2026-109619 is caused by a use-after-free vulnerability in PHP's global data structures. Exploitation can lead to system compromise, data theft, malware installation, and access to internal networks.
⚙️ The PHP Foundation had known about the root cause since 2024 but prioritized a fix only on August 11, 2026. Updates planned for October 22 were released a day early due to an embargo breach. Users should upgrade to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or install patched Linux distribution packages. For unsupported branches, migration to a supported version is recommended. Meanwhile, restrict Internet access and apply configuration-based workarounds. For network devices, install vendor fixes or apply recommended mitigations.
Positive Technologies implemented protections using PT AF, PT NAD, and PT NGFW, and released detection rules for MaxPatrol VM.
🛠 GitHub hosts over 1,000 public PHP2Shell exploit repositories, but achieving RCE against a specific target remains difficult. Exploitation requires a tailored exploit compatible with the target's PHP build, SAPI, extensions, and runtime configuration.
👾 Both vulnerabilities were added to CISA KEV on October 26. Confirmed exploitation remains limited, mostly involving network devices.
On October 26, Dream Group reported attacks on Palo Alto Networks devices in the US, Japan, Taiwan, and South Korea. Attackers identified 240 targets among 19,000 devices and compromised 24 firewalls and one management server. Three reportedly belonged to US government infrastructure. The attacks exploited PHP2Shell and the Linux kernel LPE vulnerability Fragnesia (CVE-2026-46300). Attackers stole service account credentials, user and group lists, network configurations, and private keys.
On November 12, Check Point experts reported attacks against Security Gateway devices that had started on October 30. By exploiting PHP2Shell and the DynamicCLI LPE vulnerability (CVE-2026-123039), attackers gained initial access, escalated their privileges, and installed the TSGA backdoor along with its network component, TSProxy. During the destructive phase of the attacks, they also gained SSH access to a VMware ESXi host and executed the destroy_v6 wiper.
🌐 According to Censys data, 27 million PHP services exposed to the Internet remain unpatched. In addition, the vulnerabilities affect products from numerous vendors, including Palo Alto Networks, Check Point, Netgate, Coolify, and Cisco.
@avleonovcom #PHP #PHP2Shell #PHPFoundation #UAF #OOM #LinuxPatchWednesday #LinuxKernel #SAPI #SSH #Fragnesia #DynamicCLI #VMware #ESXi #SGA #TSProxy #destroyv6 #LDAP #CISA #CISAKEV #PaloAlto #PanOS #CheckPoint #Cisco #Netgate #Coolify #Censys #GitHub #DreamGroup #LPE #Backdoor #MaxPatrolVM #PTAF #PTNAD #PTNGFW
ещё
19
3
3 14 ноя, 02:00
November Microsoft Patch Tuesday. A total of 1,093 vulnerabilities. For comparison, there were 1,409 in October, a decrease of 22.4%. Ten products had 20 or more vulnerabilities fixed: Microsoft Office Excel (64), Microsoft Office Word (61), Microsoft SQL Server (50), Windows Advanced Rasterization Platform (37), Windows Installer (36), Windows Graphics Kernel (35), Windows Kernel (28), Microsoft Office SharePoint (26), Windows DNS (21), Windows Print Spooler Components (20). Together, these products had 378 vulnerabilities fixed, or slightly more than one-third (34.6%) of the total. One vulnerability is flagged as having been exploited in the wild:
🔻 Spoofing - Microsoft Outlook (CVE-2026-124194). Microsoft Outlook is a Microsoft application for managing email, calendars, scheduling meetings, organizing contacts, and setting reminders. An attacker sends a specially crafted message file and convinces a user to open it. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, which discloses the user’s NTLMv2 hash. The attacker can use that hash to authenticate as the user. The Preview Pane is not an attack vector. A public exploit for the vulnerability is available on GitHub.
There are two vulnerabilities with public exploits, but no evidence of exploitation in the wild has been observed so far.
🔸 EoP - Microsoft Windows App Store (CVE-2026-119987). Microsoft Store (Windows App Store) is Microsoft's official app store for finding, downloading, and installing applications, games, and other digital content on Windows devices. Untrusted search path in Microsoft Windows App Store allows an authorized attacker to elevate privileges locally. A PoC was published on GitHub but later removed. A copy is available on Vulners.
🔸 EoP - Windows AppX Deployment Service (CVE-2026-116714). Windows AppX Deployment Service is a Windows system service responsible for installing, updating, and removing applications. An attacker who successfully exploited this vulnerability could gain SYSTEM privileges.
Other notable vulnerabilities include:
🔹 RCE - Windows LDAP (CVE-2026-119958). Windows LDAP is a service and protocol used to search and manage information about users, computers, and other resources in an enterprise network. An out-of-bounds write vulnerability allows an unauthorized attacker to execute arbitrary code by sending specially crafted LDAP requests over the network.
🔹 RCE - Windows Search / Exchange Server (CVE-2026-116928). An unauthenticated attacker could exploit the Windows Search component used by Microsoft Exchange Server (Microsoft's server platform for managing enterprise email, calendars, contacts, and shared meeting scheduling) by sending an email containing a specially crafted attachment. Exchange automatically processes the attachment for indexing, so the recipient does not need to open the email or attachment. Successful exploitation could allow the attacker to execute code with the permissions of the affected processing service.
[ Read the full post on avleonov.com ]
🗒 Full Vulristics report
@avleonovcom #Microsoft #PatchTuesday #AD #AppStore #AppX #DNS #Excel #Exchange #exploit #LDAP #NTLM #NTLMrelay #Office #Outlook #Schannel #SharePoint #SQLServer #VFP #Vulners #Vulristics #WindowsGraphics #WindowsARP #Windows #WindowsInstaller #WindowsKernel #WindowsSearch #Word #PrintSpooler
ещё
17
2
3 12 ноя, 00:04
Продолжить анализ этого канала
- История роста подписчиков
- Просмотры и охваты публикаций
- Кто упоминает канал и кого упоминает он
- Похожие каналы и подбор для рекламы
Открыть аналитику
Демо до 14 дней