Bug 741382 (CVE-2011-3707) - CVE-2011-3707 php-pear-Auth-OpenID: installation path disclosure via a direct request to a .php file
Summary: CVE-2011-3707 php-pear-Auth-OpenID: installation path disclosure via a direct...
Alias: CVE-2011-3707
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 741383
TreeView+ depends on / blocked
Reported: 2011-09-26 17:42 UTC by Vincent Danen
Modified: 2019-09-29 12:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-26 18:18:37 UTC

Attachments (Terms of Use)

Description Vincent Danen 2011-09-26 17:42:16 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2011-3707 to
the following vulnerability:

Name: CVE-2011-3707
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3707
Assigned: 20110923
Reference: http://www.openwall.com/lists/oss-security/2011/06/27/6
Reference: http://code.google.com/p/inspathx/source/browse/trunk/paths_vuln/%21_README
Reference: http://code.google.com/p/inspathx/source/browse/trunk/paths_vuln/auth

JanRain PHP OpenID library (aka php-openid) 2.2.2 allows remote
attackers to obtain sensitive information via a direct request to a
.php file, which reveals the installation path in an error message, as
demonstrated by Auth/Yadis/Yadis.php and certain other files.

Comment 1 Vincent Danen 2011-09-26 17:43:13 UTC
Created php-pear-Auth-OpenID tracking bugs for this issue

Affects: fedora-all [bug 741383]

Comment 2 Kurt Seifried 2011-09-26 18:18:28 UTC
NOTABUG: The Fedora packages install php-pear-Auth-OpenID to /usr/share/pear/Auth_OpenID/ outside the webroot and there is no mapping/etc. to expose that directory.

Also it appears this bug was originally reported by yehg.net to Google, Yehg sources:


indicate that some PHP apps ship a static copy of php-pear-Auth-OpenID within their files and expose them within the webroot.

Note You need to log in before you can comment on or make changes to this bug.