public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202301-09 ] protobuf-java: Denial of Service
Date: Wed, 11 Jan 2023 05:19:57 -0000	[thread overview]
Message-ID: <167341439722.8.15589571206955132511@2ac734cbf5a7> (raw)

[-- Attachment #1: Type: text/plain, Size: 2659 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202301-09
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Low
    Title: protobuf-java: Denial of Service
     Date: January 11, 2023
     Bugs: #876903
       ID: 202301-09

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

A vulnerability has been discovered in protobuf-java which could result
in denial of service.

Background
==========

protobuf-java contains the Java bindings for Google's Protocol Buffers.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-java/protobuf-java     < 3.20.3                    >= 3.20.3

Description
===========

Inputs containing multiple instances of non-repeated embedded messages
with repeated or unknown fields causes objects to be converted back and
forth between mutable and immutable forms, resulting in potentially long
garbage collection pauses.

Impact
======

Crafted input can trigger a denial of service via long garbage
collection pauses.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All protobuf-java users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-java/protobuf-java-3.20.3"

References
==========

[ 1 ] CVE-2022-3171
      https://nvd.nist.gov/vuln/detail/CVE-2022-3171
[ 2 ] CVE-2022-3509
      https://nvd.nist.gov/vuln/detail/CVE-2022-3509
[ 3 ] CVE-2022-3510
      https://nvd.nist.gov/vuln/detail/CVE-2022-3510

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202301-09

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2023 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-01-11  5:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167341439722.8.15589571206955132511@2ac734cbf5a7 \
    --to=glsamaker@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox