Git Users Urged to Update Software to Prevent Remote Code Execution Attacks

Jan 18, 2023

Jan 18, 2023Ravie LakshmananDevOpsSec / Software Security

The maintainers of the Git ^[1]
source code version control system have released updates to
remediate two critical vulnerabilities that could be exploited by a
malicious actor to achieve remote code execution.

The flaws, tracked as CVE-2022-23521^[2] and CVE-2022-41903^[3], impacts the following
versions of Git: v2.30.6, v2.31.5, v2.32.4, v2.33.5, v2.34.5,
v2.35.5, v2.36.3, v2.37.4, v2.38.2, and v2.39.0.

Patched versions include v2.30.7, v2.31.6, v2.32.5, v2.33.6,
v2.34.6, v2.35.6, v2.36.4, v2.37.5, v2.38.3, and v2.39.1. X41 D-Sec
security researchers Markus Vervier and Eric Sesterhenn as well as
GitLab’s Joern Schneeweisz have been credited with reporting the
bugs.

“The most severe issue discovered allows an attacker to trigger
a heap-based memory corruption during clone or pull operations,
which might result in code execution,” the German cybersecurity
company said ^[4]
of CVE-2022-23521.

CVE-2022-41903, also a critical vulnerability, is triggered
during an archive operation, leading to code execution by way of an
integer overflow flaw that arises when formatting the commit
logs.

“Additionally, a huge number of integer related issues was
identified which may lead to denial-of-service situations,
out-of-bound reads or simply badly handled corner cases on large
input,” X41 D-Sec noted.

While there are no workarounds for CVE-2022-23521, Git is
recommending that users disable “git archive” in untrusted
repositories as a mitigation for CVE-2022-41903 in scenarios where
updating to the latest version is not an option.

GitLab, in a coordinated advisory, said ^[5]
it has released versions 15.7.5, 15.6.6, and 15.5.9 for GitLab
Community Edition (CE) and Enterprise Edition (EE) to address the
shortcomings, urging customers to apply the fixes with immediate
effect.

Found this article interesting? Follow us on Twitter ^[6]
and LinkedIn ^[7]
to read more exclusive content we post.

References

^{^}
Git
(git-scm.com)
^{^}
CVE-2022-23521
(github.com)
^{^}
CVE-2022-41903
(github.com)
^{^}
said
(x41-dsec.de)
^{^}
said
(about.gitlab.com)
^{^}
Twitter
 (twitter.com)
^{^}
LinkedIn
(www.linkedin.com)

The Hacker News Headlines

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

Aug 18, 2023

The Hacker News Headlines

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

Aug 18, 2023

The Hacker News Headlines

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

Aug 18, 2023

OWASP TOP !0

Injection. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization. Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently. Sensitive Data Exposure. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser. XML External Entities (XXE). Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks. Broken Access Control. Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc. Security Misconfiguration. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion. Cross-Site Scripting XSS. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites. Insecure Deserialization. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks. Using Components with Known Vulnerabilities. Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts. Insufficient Logging & Monitoring. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Git Users Urged to Update Software to Prevent Remote Code Execution Attacks

References

Related Post

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

You missed

Protected: Rotary VI EAST

Protected: BetterCyberCareer Group

Protected: Benin Club 1931 – Official

Protected: Whatsapp AI Automation Group