Bug 50602 - non thread safe functions used in apache httpd project - ap_uname2id ap_gnamed2id
Summary: non thread safe functions used in apache httpd project - ap_uname2id ap_gname...
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.17
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2011-01-17 09:19 UTC by Kevin J Walters
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin J Walters 2011-01-17 09:19:50 UTC
Whilst looking at a thread safety issue in mod_fastcgi, i noticed
there's some suspicious looking code in apache httpd project.

server/mpm_common.c (2.2.17) has two functions ap_uname2id and
ap_gname2id which call getpwnam and getgrnam, two non-reentrant
functions.

Comparing with typical apr code that tends to have an #ifdef to
select function() vs function_r().

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

Perhaps ap_uname2id and ap_gname2id are not executed concurrently by
the current code base but if these are general purpose functions they
should be more cautious/safe?

Has the whole apache httpd 2.x project been scanned for use of
non-reentrant function calls?

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

Email thread in dev mailing list - http://marc.info/?l=apache-httpd-dev&m=129482822402732&w=2
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:58 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.