CVE-2020-12658

gssproxy (aka gss-proxy) before 0.8.3 does not unlock condmutex before pthread exit in gpworkermain() in gpworkers.c. NOTE: An upstream comment states "We are already on a shutdown path when running the code in question, so a DoS there doesn't make any sense, and there has been no additional information provided us (as upstream) to indicate why this would be a problem.

References

Affected packages

Debian:11 / gssproxy

Package

Name: gssproxy
Purl: pkg:deb/debian/gssproxy?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Affected versions

0.*

0.8.2-2

0.8.4-1

0.8.4-2

0.9.1-1

0.9.2-1

0.9.2-2

0.9.2-3

Ecosystem specific

{
    "urgency": "unimportant"
}

Debian:12 / gssproxy

Package

Name: gssproxy
Purl: pkg:deb/debian/gssproxy?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Affected versions

0.*

0.9.1-1

0.9.2-1

0.9.2-2

0.9.2-3

Ecosystem specific

{
    "urgency": "unimportant"
}

Debian:13 / gssproxy

Package

Name: gssproxy
Purl: pkg:deb/debian/gssproxy?arch=source

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Affected versions

0.*

0.9.1-1

0.9.2-1

0.9.2-2

0.9.2-3

Ecosystem specific

{
    "urgency": "unimportant"
}

Git / github.com/gssapi/gssproxy

Affected ranges

Type: GIT
Repo: https://github.com/gssapi/gssproxy
Events: Introduced

0 Unknown introduced commit / All previous commits are affected

Fixed

cb761412e299ef907f22cd7c4146d50c8a792003

Fixed

cb761412e299ef907f22cd7c4146d50c8a792003

Affected versions

v0.*

v0.8.0

v0.8.1

v0.8.2