Re: CVE Request: pgbouncer: DoS/remote crash: invalid packet order causes lookup of NULL pointer

[cve-assign () mitre org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> https://pgbouncer.github.io/2015/04/pgbouncer-1-5-5/
> https://github.com/pgbouncer/pgbouncer/issues/42
> https://github.com/pgbouncer/pgbouncer/commit/edab5be6665b9e8de66c25ba527509b229468573
> https://github.com/pgbouncer/pgbouncer/commit/74d6e5f7de5ec736f71204b7b422af7380c19ac5

> Fix remote crash - invalid packet order causes lookup of NULL pointer. Not exploitable, just DoS.

Use CVE-2015-4054.

issues/42 says "we're suffering from a segmentation fault every now
and then on CentOS6 x86_64 with pgbouncer 1.5.4. The instance is
dying" and lists 5 different PIDs. As far as we can tell, this means
that each segmentation fault caused a complete pgbouncer outage, and
pgbouncer was then restarted manually or with a third-party monitoring
program. We don't think the report means that an "instance" crashed
and pgbouncer itself continued with no outage (that type of issue is
often outside the scope of CVE, if it means that a single client is
essentially conducting a DoS attack against its own service). Also, as
far as we can tell, an outage doesn't depend on whether -d was used.

- -- 
CVE assignment team, MITRE CVE Numbering Authority
M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through http://cve.mitre.org/cve/request_id.html ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (SunOS)

iQEcBAEBAgAGBQJVXyrFAAoJEKllVAevmvms/qEH/08RKvuaPUXOdG1oqRQXSBuv
yu8MVbaDuRcsMv9LoKyo2arMD7gsTstaRkrf5yZU8WDtbE1R5vqIjzMl7Bt6nzSY
aBBCxFjqlR4tuEbuZTmSBcWTHvVtkoFSwr3pegqUzEKL/3e0xL1/DxQtdRseXAIv
Kzvsatm0lOCxI+TIjMWp7OHgb8rgp4DLXtCs2zr13uUph6Ff8rU0Gq1vx9lM8GMD
+7FVHAYXUP98w38tMstWojXriKdXN5oJQ+K+W8QinQsALeNduTI7EqUvhkE1aqCi
MTPGVqkKKxsynQJsoPzdjQvWEqYGVDDN3icRNY9Ej4ZVUuKETFHhN3Kn4dp2Oso=
=DLec
-----END PGP SIGNATURE-----