{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:467ecc61-20b2-596b-bd12-dc2943b32799", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.2.post11+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.2.post11+tuxcare", "version": "5.0.2.post11+tuxcare", "pedigree": { "ancestors": [ { "name": "django", "purl": "pkg:pypi/django@5.0.2", "type": "library", "version": "5.0.2" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2007-0404", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:408f5cb6-5480-5b39-a5a8-0a42aae8c670", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a9391805-9c4e-5007-9dfa-b2ad16ad3b1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:81c4c2cd-2f45-519a-b2d4-e132c54fb317", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9d8b5734-f810-5e03-ab18-408371fca673", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b27aec43-9530-5a93-b613-103f8987fa75", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ba312817-289c-596d-bab5-85d18a5e06cd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:558232da-e8a5-5d6d-b8bc-a59220eef83d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1f06db1a-df2e-5461-84d2-951f2c29ff37", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:739835a8-55ee-5fad-9aa6-5a8d4f85cdd6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e445c048-1c53-57da-ac8b-63760e0ee7f9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:777bdf34-2a54-5c54-8ad6-501867eb25df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:214ed97e-e846-5057-b4f8-ca934b10b8b1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7d1b46a3-2e96-5526-bd24-1e7834b9ac9f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a35c9876-fc4b-5ce4-92ba-55ccde7ffd97", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2147ff2e-ef13-5fa8-8b3f-3ad704690976", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1bdae73d-9695-57a1-b6a2-a6711d35c6dd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ff84e4ac-1d86-5fa0-a2bc-5c0dc11e1d79", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3a9a0e15-8778-51e0-85d5-20858b984543", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ef0ca29e-e62f-586f-852d-79ac7c6a2205", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:37b675f0-2011-5831-ae01-8a8d3274c985", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9fbb23f0-9619-5d4c-8193-b0796d4aa426", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:944c008d-fb14-54d8-b905-e524ef661c20", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1ce380a6-b679-54bf-867f-391f2fca15af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:eac3582b-8a6c-555d-86d8-440339ff381f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9bfa3648-fd51-5720-ba9f-1529b55f9079", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c44bafa0-7231-5c2c-86c2-2288b549013e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:077b60e4-0278-57d4-91ed-762d8c152130", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:963262db-71a4-55f7-b4ec-13ce760cb144", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0a73b23d-9502-5900-9b5d-80b6842fa447", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3e378543-4efd-509f-b240-3692244a0c25", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4cf2db2d-205d-5e09-84d4-df2b5e8cea3f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0fcbf2d3-ff02-5dd7-b4d8-0effd5e90f48", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:75b8ceb9-f82e-5584-ac9a-ee4a48e3ce44", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ba5eab4b-c205-5713-9eac-aab1ec59279d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dea59716-b7ec-5940-9924-081bb8d0bb7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:66fef355-ff05-54b3-87a3-22f5fc9f6895", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1958a476-d379-591a-a8c9-21ff2df73faa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0bcca87b-70a1-58f5-ad45-fe7e0914ab88", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e11e37f3-1cfb-5b8e-96f2-e4d074560c22", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a1b593a1-a756-5cfd-a0e9-ea7823f1d98c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4b11778c-2323-54c6-8ab1-9b3f18181949", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b452b0e6-516e-54c8-8546-cefdbea1dcbe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:38758491-6947-580e-83a5-53712fba91af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8bc375b9-7fee-57e0-b266-c05361aa630b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a2a183b4-fdf7-5fb3-8ce4-24b8be44009f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:cb5dea92-c3f2-578f-ae7f-09a94beee607", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0fd0d0db-8e1d-5e77-bc6f-359df9e4b62e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f9753b5d-9116-5a71-aa1e-ebe0fbbf17d2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5a8071cb-71c8-5dbd-9425-19df3ffe0d22", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:69dfd4a2-b486-50e7-b8e3-f2feb5708ef5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3c967cdb-cdf9-5dd2-8641-5765bf45c7d8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:08da054c-d954-515a-a64d-bf3f11648a26", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f6597967-8dae-5cbd-8ef3-c32051afb121", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:78da3715-aaf4-553b-8d47-19a15727c240", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:db72d06e-8c7e-56b3-af52-8117f37eb807", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f410e190-f594-5382-a675-a12af6898570", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:90db9162-b729-5afb-b0b8-3d24a1582dc8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:fc65f519-3e07-5450-bfa8-9fb78a64619e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dd6dea8b-b57e-5dfe-b1fd-c741168e24e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:87c9f5d5-323e-5c3e-9574-49a2bd321331", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c52042a2-fb16-5d9e-b878-f1681621590a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8b421f32-8d50-5c08-a174-3979c7fe24e1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:32fc0240-0329-5ebb-8b23-3944172cb0b8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:29efca1a-d5c0-5e03-98f4-0efa95e72ddf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ab084f2d-08c5-52d9-bf3a-d867ccf44006", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5c56252f-ee5a-5f97-a23f-5e53a27c079f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5e1b4804-4b68-5135-b5c9-3119765a8989", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e0faba37-8aaa-5b97-8e6a-c26026926fc0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:d8406c4b-f71e-54ea-a5aa-697ce8b98007", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:27bea56c-d5f3-52ed-a55b-586e4468d97a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a7c17670-1005-5b3d-9bf7-e3caa96b3c5d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:22553977-44bc-5b8d-9cb9-eb3bb2285634", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ed7c053d-df04-5e9b-a09c-6fa2f6da4371", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:acb4bec4-d8b6-52bb-ae96-3753d21d7539", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:613c5e5a-9f14-5b5e-bf09-d579e88060c4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5c7fd4c5-8d19-5ab7-82a9-6d5f9295ddbd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:db59a991-cc43-5c75-ae66-a476339feecb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:77c2bb02-2621-5c0b-a05f-bc16ccadb02d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9a31c360-3e19-51e6-9f7d-3150b305adf9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:102bf8dd-e7d7-5f2d-9cf5-a88388f38ddf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:cbf3846b-87a2-5efc-8342-d69be762f6e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e1f9f5ba-d0b8-5469-b478-2e3b905b2836", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ffed3370-4410-5b2d-aa8f-0ebc971bcfd5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b44cb336-f32a-5ae3-a797-8bdc03c4ec1f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4ac37a4f-fcad-59e3-80e5-5ebefa62a546", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0a6cc604-5554-5bcb-a30a-d7723aecbd94", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4784878f-f2b9-522c-acfc-da2133753169", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:317197d1-9a93-5ac5-86be-0a3e592b723e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:d124fe67-3ae3-55d1-90c6-79011fc8ceee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:21e55bfe-13b3-5815-b3a3-5240716c411b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e9416b6a-e08b-50f1-a230-8de25ade9141", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e513a517-75ea-5f4d-b9f6-500cc51835fd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:18913280-38ca-53cd-8873-adb1fe4e274a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:699106ef-555c-5e72-82e3-050d5bc50521", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2f4dda3e-b324-5d28-85b4-f91bea7359da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:20e2360a-4881-5325-a41e-7f1e0c249756", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 is NOT affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed by upstream Django in version 4.0.1 (January 2022), over 2 years before Django 5.0.2 was released (February 2024). All required defenses are present in the target: backslash normalization, path traversal detection via \"..\" checks, os.path.relpath() to ensure relative paths, and trip...", "justification": "code_not_present" } }, { "id": "CVE-2022-22818", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1b2e6bb2-adb7-552b-a195-09f05c80e14f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Target Django 5.0.2 is not affected by CVE-2022-22818. The vulnerability (unescaped HTML output in {% debug %} template tag leading to XSS) is not present because the upstream Django fix was already included in the 5.0.2 release. The DebugNode.render() method contains both security measures: (1) early return when DEBUG=False, and (2) HTML escaping via escape() on all pformat outputs. CVE affect...", "justification": "code_not_present" } }, { "id": "CVE-2022-23833", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:29536f80-34d8-5b5c-b4c9-349fc0585e0d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:42484094-9f04-5ad2-bdec-97045d89b3d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:12700030-3e29-5f1e-ab59-a91878a63184", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:80357817-6de1-54f9-ac1a-f51e05635281", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3357e846-8757-56e2-96dd-264125987352", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:86d9b5a4-5ca3-59b3-83bb-498cb518b457", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dd961d73-6732-5cb4-ab42-fb24585fe4e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:44f0b2b1-d280-57f7-82a8-a9412b034b3e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4c6c0cc1-b103-56d6-b662-79cacd0d869c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7fa868f0-c4f6-58be-992f-d861fa8affda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:54876906-0fb5-547c-b6c7-eb67f66e52ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2b6deb53-b702-5a7c-ae14-b33e84bcaddb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7af6837d-c7a3-59f9-88f9-b28450ea20a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:30a6124e-be51-5e3d-9b60-6888a9036054", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8d2fedcc-bb18-5b6b-b2da-2289aaae7523", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:85212a61-3dab-5126-b782-ceabd98b3709", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8a8269f5-2dae-5244-a500-c4d90d7d9001", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:30e836ff-bc4c-5278-a015-a0b8af82cd25", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8ac4053b-24af-5222-ab41-e27b62b4cf61", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:04475b98-7d62-5e51-a414-e9399c18c913", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:043cef8a-86f3-56ac-9c34-8831833a556d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41990 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 uses the original simple trim_punctuation implementation that lacks the vulnerable code pattern. CVE-2024-41990's DoS vulnerability was introduced by the CVE-2024-38875 fix (commit d666457453, June 2024) which replaced the simple implementation with a complex CountsDict-based one containing repeated rfind('&') calls. The target version predates this architectural change and therefo...", "justification": "code_not_present" } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dac4c20c-5a0b-578d-9b36-d8024846f147", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dd35f60a-0e0d-5d33-b7dd-ccfbcc6b778d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:98487094-2748-5b07-aa1e-168318824521", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3dcd2473-0521-509a-93c1-986f00c1efb6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5c7118ff-6284-5a8e-a1b7-671a8ecc5886", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5e9bd4f9-76e1-5fb5-8dbf-f4828334d7d4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0aa0e199-236d-5221-99bc-9d7d0da2e40f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8049cea9-6de3-5636-b1c1-186ac85762c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e9462130-a8c8-5bbf-bfad-f5bec8baff2c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7f86b186-2570-5230-8da3-d6d33d16ea8b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:615a123e-7ec2-545e-b2ab-b6a030b93408", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:01926c81-3364-5382-b94c-4dce2cf4a30b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5674235e-50a4-5cbd-83c0-a96d6626a9a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c75ff64c-470a-5f73-ae66-6f2f2b5237a5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:81df920e-94e9-5e71-8194-bdeebff0ebcd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8f8add7f-be44-5e88-aef9-efab39fea876", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 5.0.2.post11+tuxcare of django. CVE-2025-59681 already fixed on tuxcare-current/5.0.2 by 96d64ebe98, released in 5.0.2.post7+tuxcare; FORBIDDEN_ALIAS_PATTERN matches upstream stable/4.2.x; alias 'x#' rejected on 5.0.2.post16 from Nexus." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:afda2b5f-a3aa-5d60-a308-abd3b1365c96", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post15+tuxcare." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8822addf-9d77-55f7-8381-00cf55abe2ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:13a81706-1ccb-5061-93bf-33cb6ba3d9b0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9eb166af-eea9-50bc-9ad2-699b36cda16c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2315f4ae-a8d3-5974-8ca5-15437efecf2c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:76ba7c1c-bc10-5a2c-b6eb-1a89ef50a16d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4cf5b0f9-7f73-582e-abc2-09bfcf7c7410", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4221981f-df7d-5c28-8e3d-36cc7e2ef1c8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:844e6085-004c-5d89-8379-10374b01d1c4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0b919d44-3bc6-57ca-8939-22ec0da9b782", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c3a53b81-0189-5b8c-b2fa-49e1d623d0bb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:18acf11d-00ef-52c4-8d98-80125c6bdc49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post12+tuxcare." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6a54f641-91d4-512c-8298-1d98517e6b3d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6d13c0cf-01ff-56f4-91ea-7cd813550fd1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6f23cb45-11c1-5a8a-8985-ee08383a3ecf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:001df9f6-6f6c-5f82-89fd-e5ca2e1fc298", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1f7d2b51-5595-5a49-9555-45cf2bbb2354", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c262ee05-4158-509b-b916-0ea0ee9063d4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:63db3dbc-3de5-533c-a465-48df3b82d05c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9e2eb1f7-1531-5ae5-8617-b3262811fc2c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:74ec95f1-1250-50c0-b685-82a230b2f2e9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2933f06b-6dfb-56ae-9623-d15b084ac4f8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3766c3eb-fd65-5cbe-94fe-ede3ca89d7d9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post16+tuxcare." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:605af7aa-bda6-51ab-a2f4-48b4e0ba642b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post16+tuxcare." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:75401077-e8c4-5a88-a7b5-dfe7069bca51", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post16+tuxcare." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:db0b421f-bd97-5972-90f3-a1aad4ab70c4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:bd40b186-7829-50aa-8d0c-66fddf1e0fdd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f3453d91-ab3c-5f12-82cd-39bd1636dfa6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f81dc1ec-ec80-5530-86ce-e0ede7071ed6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 is not affected by CVE-2026-53878. The vulnerable code (DomainNameValidator class) does not exist in this version - it was introduced in Django 5.1. Django 5.0.2 uses _simple_domain_name_validator which already validates against newlines via string.whitespace.", "justification": "code_not_present" } }, { "id": "CVE-2026-5766", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:21dcfa79-fb79-5f65-a74b-2dfe43b87ba9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5476710d-9018-59e7-9de9-91e4219d40f0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4bc5431f-72f7-5d7d-becd-e1c3c210eff1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:071f352b-8c55-505d-b557-6868e2bac353", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4323db6f-1dd3-555e-bbd3-9206059a5231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.2.post11+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ] }