CVE-2022-35920

sanic vulnerable to Path Traversal when using app.static if using encoded %2F URLs

References

https://github.com/sanic-org/sanic/issues/2478
https://github.com/sanic-org/sanic/pull/2495

For more information

If you have any questions or comments about this advisory:

• Open an issue in the community forums
• Ping us on the Discord server

Access to lateral directories when using app.static if using encoded %2F URLs. Parent directory traversal is not impacted.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-35920 has a CVSS score of 8.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (22.6.1, 21.12.2, 20.12.7); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

• v20.12.7 (LTS)
• v21.12.2 (LTS)
• v22.6.1

1. What is CVE-2022-35920? CVE-2022-35920 is a high-severity path traversal vulnerability in sanic (pip), affecting versions >= 22.0.0, < 22.6.1. It is fixed in 22.6.1, 21.12.2, 20.12.7. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-35920? CVE-2022-35920 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sanic are affected by CVE-2022-35920? sanic (pip) versions >= 22.0.0, < 22.6.1 is affected.
4. Is there a fix for CVE-2022-35920? Yes. CVE-2022-35920 is fixed in 22.6.1, 21.12.2, 20.12.7. Upgrade to this version or later.
5. Is CVE-2022-35920 exploitable, and should I be worried? Whether CVE-2022-35920 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-35920 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-35920?
   • Upgrade sanic to 22.6.1 or later
   • Upgrade sanic to 21.12.2 or later
   • Upgrade sanic to 20.12.7 or later

Other vulnerabilities in sanic