Google on Friday shipped an out-of-band security update to
address a high severity vulnerability in its Chrome browser that it
said is being actively exploited in the wild.

Tracked as CVE-2022-1096[1], the zero-day flaw
relates to a type confusion vulnerability in the V8 JavaScript
engine. An anonymous researcher has been credited with reporting
the bug on March 23, 2022.

Type confusion errors, which arise when a resource (e.g., a
variable or an object) is accessed using a type that’s incompatible
to what was originally initialized, could have serious consequences
in languages that are not memory safe[2]
like C and C++, enabling a malicious actor to perform out-of-bounds
memory access.

Automatic GitHub Backups

“When a memory buffer is accessed using the wrong type, it could
read or write memory out of the bounds of the buffer, if the
allocated buffer is smaller than the type that the code is
attempting to access, leading to a crash and possibly code
execution,” MITRE’s Common Weakness Enumeration (CWE) explains[3].

The tech giant acknowledged it’s “aware that an exploit for
CVE-2022-1096 exists in the wild,” but stopped short of sharing
additional specifics so as to prevent further exploitation and
until a majority of users are updated with a fix.

CVE-2022-1096 is the second zero-day vulnerability addressed by
Google in Chrome since the start of the year, the first being
CVE-2022-0609[4], a use-after-free
vulnerability in the Animation component that was patched on
February 14, 2022.

Prevent Data Breaches

Earlier this week, Google’s Threat Analysis Group (TAG) disclosed[5]
details of a twin campaign staged by North Korean nation-state
groups that weaponized the flaw to strike U.S. based organizations
spanning news media, IT, cryptocurrency, and fintech
industries.

Google Chrome users are highly recommended to update to the
latest version 99.0.4844.84 for Windows, Mac, and Linux to mitigate
any potential threats. Users of Chromium-based browsers such as
Microsoft Edge, Opera, and Vivaldi are also advised to apply the
fixes as and when they become available.

References

  1. ^
    CVE-2022-1096
    (chromereleases.googleblog.com)
  2. ^
    memory
    safe
    (en.wikipedia.org)
  3. ^
    explains
    (cwe.mitre.org)
  4. ^
    CVE-2022-0609
    (thehackernews.com)
  5. ^
    disclosed
    (thehackernews.com)

Read more