OpenWISP Controller CA CRL REST API does not scope requests to managed organizations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenWISP Controller, a network and WiFi provisioning and PKI management tool, is affected. An authenticated organization manager with certificate authority view permission can download the certificate revocation list of another organization's CA, which can reveal CA issuer details and revoked certificate serial numbers.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
OpenWISP Controller is a network and WiFi controller for provisioning, configuration management, updates, and PKI management. From 1.0.0 until 1.3.2, the GET /api/v1/controller/ca/<integer-id>/crl endpoint allows an authenticated organization manager with CA view permission to retrieve another organization's certificate revocation list by requesting its sequential CA identifier. CrlDownloadView.retrieve resolves the CA directly instead of using the organization-scoped object retrieval enforced by FilterByOrganizationManaged, bypassing the endpoint's intended authorization boundary. The response can disclose CA issuer information and revoked certificate serial numbers, but it does not expose CA private keys or allow modification. This issue is fixed in version 1.3.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openwisp openwisp-controller
From 1.0.0 · fixed in 1.3.2