Issue #137: Imporper handling of security context on error - gssproxy - Pagure.io

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

gssproxy

#137 Imporper handling of security context on error

Closed: Fixed Opened Feb 27, 2015 by simo.

When an error happens during security context establishment we do not always properly handle the input/output pointer and in some cases we do not null out a pointer after we freed the pointed memory.
This may cause clients to then call gss_delete_sec_context and run into a double-free issue.

Found via: https://bugzilla.redhat.com/show_bug.cgi?id=1196371

simo commented Feb 27, 2015

Patch for the issue
0001-Properly-handle-security-contexts-on-error.patch

simo commented Mar 26, 2015

Fixed in: ab69b71

dpal commented Apr 16, 2015

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1196371 (Red Hat Enterprise Linux 7)

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: 2015 March

Feb 28, 2017

Metadata

Assignee

Tags

None

Blocking

None

Depending on

None

Priority

Lowest

type

defect

component

mechglue interface

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.