GHSA-qrmm-w4v4-q7f8
GHSA-qrmm-w4v4-q7f8 is a security vulnerability in docassemble. O3 Security confirms whether GHSA-qrmm-w4v4-q7f8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Unauthorized access through URL manipulation
Real-World Exposure
docassembleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The vulnerability allows attackers to gain unauthorized access to information on the system through URL manipulation.
Patches
The vulnerability has been patched in version 1.2.65 of the master branch, version 1.1.113 of the 1.1.x series, and version 1.0.12 of the stable branch. The Docker image on docker.io has been patched.
Workarounds
If upgrading is not possible, manually apply the changes of https://github.com/jhpyle/docassemble/commit/e3dbf6ce054b3c0310996f0657289f5eed0a73fe and restart the server (e.g., by pressing Save on the Configuration screen).
Credit
The vulnerability was discovered by Jim Platania of Seiso LLC (@jimmio).
For more information
If you have any questions or comments about this advisory:
- Open an issue in docassemble
- Join the Slack channel
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | docassemble | all versions | 1.2.65 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for docassemble. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update docassemble to 1.2.65 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrmm-w4v4-q7f8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qrmm-w4v4-q7f8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qrmm-w4v4-q7f8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qrmm-w4v4-q7f8 in your dependencies?
O3 detects GHSA-qrmm-w4v4-q7f8 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.