CVE-2017-1002151
published 2017-09-14CVE-2017-1002151: Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
PriorityP334high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | pagure | — | — |
| pagure_project | pagure | >= unspecified < 3.3.0 | 3.3.0 |
| redhat | pagure | <= 3.3 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
vendor_debian7.5LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2017-1002151: pagure - Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper...
vendor_debian·2017·CVSS 7.5
CVE-2017-1002151 [HIGH] CVE-2017-1002151: pagure - Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper...
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
Scope: local
bullseye: resolved
sid: resolved
trixie: resolved
GHSA
GHSA-m5c9-mwvj-33fc: Pagure 3
ghsa_unreviewed·2022-05-13
CVE-2017-1002151 [HIGH] CWE-285 GHSA-m5c9-mwvj-33fc: Pagure 3
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-1002151 pagure: Private repositories accessible through ssh [fedora-all]
bugzilla·2017-07-24·CVSS 7.5
CVE-2017-1002151 [HIGH] CVE-2017-1002151 pagure: Private repositories accessible through ssh [fedora-all]
CVE-2017-1002151 pagure: Private repositories accessible through ssh [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported vers
Bugzilla
CVE-2017-1002151 pagure: Private repositories accessible through ssh
bugzilla·2017-07-24·CVSS 7.5
CVE-2017-1002151 [HIGH] CVE-2017-1002151 pagure: Private repositories accessible through ssh
CVE-2017-1002151 pagure: Private repositories accessible through ssh
It was found that the gitolite config, which is used to configure SSH-access, allows "@all" users to access all repositories. This allows an attacker to access any private repository.
References:
http://seclists.org/oss-sec/2017/q3/204
Upstream issue:
https://pagure.io/pagure/pull-request/2426
Discussion:
Created pagure tracking bugs for this issue:
Affects: epel-7 [bug 1474270]
Affects: fedora-all [bug 1474271]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Bugzilla
CVE-2017-1002151 pagure: Private repositories accessible through ssh [epel-7]
bugzilla·2017-07-24·CVSS 7.5
CVE-2017-1002151 [HIGH] CVE-2017-1002151 pagure: Private repositories accessible through ssh [epel-7]
CVE-2017-1002151 pagure: Private repositories accessible through ssh [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedp
2017-09-14
Published