Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| - | n/a | n/a | - |
| # | POC Description | Source Link | Shenlong Link |
|---|---|---|---|
| 1 | PoC for CVE-2022-34265 (Django) | https://github.com/aeyesec/CVE-2022-34265 | POC Details |
| 2 | CVE-2022-34265 Vulnerability | https://github.com/traumatising/CVE-2022-34265 | POC Details |
| 3 | PoC for CVE-2022-34265 | https://github.com/ZhaoQi99/CVE-2022-34265 | POC Details |
| 4 | None | https://github.com/coco0x0a/CTF_Django_CVE-2022-34265 | POC Details |
| 5 | None | https://github.com/lnwza0x0a/CTF_Django_CVE-2022-34265 | POC Details |
| 6 | An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. | https://github.com/projectdiscovery/nuclei-templates/blob/main/dast/cves/2022/CVE-2022-34265.yaml | POC Details |
| 7 | None | https://github.com/Threekiii/Awesome-POC/blob/master/%E5%BC%80%E5%8F%91%E6%A1%86%E6%9E%B6%E6%BC%8F%E6%B4%9E/Django%20Trunc%28kind%29%20and%20Extract%28lookup_name%29%20SQL%E6%B3%A8%E5%85%A5%E6%BC%8F%E6%B4%9E%20CVE-2022-34265.md | POC Details |
| 8 | https://github.com/vulhub/vulhub/blob/master/django/CVE-2022-34265/README.md | POC Details |
No public POC found.
Login to generate AI POCNo comments yet