{"vulnerability": "CVE-2019-1010083", "sightings": [{"uuid": "2969138a-54ef-41bf-83dc-89654ab246b7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://gist.github.com/Ottapiens/e20fd8a5b3d73cb0ffa38013f25292e1", "content": "", "creation_timestamp": "2025-11-22T10:05:19.000000Z"}, {"uuid": "744bc4e2-5079-4192-9505-73492b1fc946", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://gist.github.com/Ottapiens/eec03543750502c92edc81d7c568d88c", "content": "", "creation_timestamp": "2025-11-22T10:06:48.000000Z"}, {"uuid": "c24d6c2a-6a4e-421b-b01c-65736c517e66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://t.me/hacking_Attack/39261", "content": "Audit dependencies in JSON format:  $ pip-audit -f json | jq\nFound 2 known vulnerabilities in 1 packages\n[\n  {\n    \"name\": \"flask\",\n    \"version\": \"0.5\",\n    \"vulns\": [\n      {\n        \"id\": \"PYSEC-2019-179\",\n        \"fix_versions\": [\n          \"1.0\"\n        ],\n        \"description\": \"The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may overlap CVE-2018-1000656.\"\n      },\n      {\n        \"id\": \"PYSEC-2018-66\",\n        \"fix_versions\": [\n          \"0.12.3\"\n        ],\n        \"description\": \"The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vu   lnerability appears to have been fixed in 0.12.3. NOTE: this may overlap CVE-2019-1010083.\"\n      }\n    ]\n  },\n  {\n    \"name\": \"jinja2\",\n    \"version\": \"3.0.2\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"pip\",\n    \"version\": \"21.3.1\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"setuptools\",\n    \"version\": \"57.4.0\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"werkzeug\",\n    \"version\": \"2.0.2\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"markupsafe\",\n    \"version\": \"2.0.1\",\n    \"vulns\": []\n  }\n]\n  Security Model  This section exists to describe the security assumptions you can and must not  make when using pip-audit.  TL;DR: If you wouldn't pip install it, you should not pip audit it.  pip-audit is a tool for auditing Python environments for packages with  known vulnerabilities. A \"known vulnerability\" is a publicly reported flaw in  a package that, if uncorrected, might allow a malicious actor to perform  unintended actions.  pip-audit can protect you against known vulnerabilities by telling  you when you have them, and how you should upgrade them. For example,  if you have somepackage==1.2.3 in your environment, pip-audit can tell  you that it needs to be upgraded to 1.2.4.  You can assume that pip-audit will make a best effort to fully resolve  all of your Python dependencies and either fully audit each or explicitly  state which ones it has skipped, as well as why it has skipped them.  pip-audit is not a static code analyzer. It analyzes dependency trees,  not code, and it cannot guarantee that arbitrary dependency resolutions  occur statically. To understand why this is, refer to Dustin Ingram's  excellent post on dependency resolution in Python (https://dustingram.com/articles/2018/03/05/why-pypi-doesnt-know-dependencies/).  As such: you must not assume that pip-audit will defend you against  malicious packages. In particular, it is incorrect to treat  pip-audit -r INPUT as a \"more secure\" variant of pip-audit. For all intents  and purposes, pip-audit -r INPUT is functionally equivalent to  pip install -r INPUT, with a small amount of non-security isolation to  avoid conflicts with any of your local environments.  Licensing  pip-audit is licensed under the Apache 2.0 License.  pip-audit reuses and modifies examples from  resolvelib, which is licensed under  the ISC license.  Contributing  See the contributing docs (https://github.com/trailofbits/pip-audit/blob/main/CONTRIBUTING.md) for details.  Code of Conduct  Everyone interacting with this project is expected to follow the  PSF Code of Conduct (https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md).  \n\nDownload Pip-Audit (https://github.com/trailofbits/pip-audit)\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:59.282883Z"}, {"uuid": "5c899e12-58d3-4474-b70b-041b15b32374", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://t.me/hacking_Attack/39260", "content": "-f FORMAT, --format FORMAT\n                        the format to emit audit    results in (choices: columns,\n                        json, cyclonedx-json, cyclonedx-xml) (default:\n                        columns)\n  -s SERVICE, --vulnerability-service SERVICE\n                        the vulnerability service to audit dependencies\n                        against (choices: osv, pypi) (default: pypi)\n  -d, --dry-run         collect all dependencies but do not perform the\n                        auditing step (default: False)\n  -S, --strict          fail the entire audit if dependency collection fails\n                        on any dependency (default: False)\n  --desc [{on,off,auto}]\n                        include a description for each vulnerability; `auto`\n                        defaults to `on` for the `json` format. This flag has\n                        no effect on the `cyclonedx-json` or `cyclonedx-xml`\n                        formats. (default: auto)\n  --cache-dir CACHE_DIR\n                           the directory to use as an HTTP cache for PyPI; uses\n                        the `pip` HTTP cache by default (default: None)\n  --progress-spinner {on,off}\n                        display a progress spinner (default: on)\n  --timeout TIMEOUT     set the socket timeout (default: 15)\n  --path PATHS          restrict to the specified installation path for\n                        auditing packages; this option can be used multiple\n                        times (default: [])\n  -v, --verbose         give more output; this setting overrides the\n                        `PIP_AUDIT_LOGLEVEL` variable and is equivalent to\n                        setting it to `debug` (default: False)\n  Exit codes  On completion, pip-audit will exit with a code indicating its status.  The current codes are:    0: No known vulnerabilities (https://www.kitploit.com/search/label/Known%20Vulnerabilities) were detected.  1: One or more known vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) were found.    Examples  Audit dependencies for the current Python environment:  $ pip-audit\nNo known vulnerabilities found\n  Audit dependencies for a given requirements file:  $ pip-audit -r ./requirements.txt\nNo known vulnerabilities found\n  Audit dependencies for the current Python environment excluding system packages:  $ pip-audit -r ./requirements.txt -l\nNo known vulnerabilities found\n  Audit dependencies when there are vulnerabilities present:  $ pip-audit\nFound 2 known vulnerabilities in 1 packages\nName  Version ID             Fix Versions\n----  ------- -------------- ------------\nFlask 0.5     PYSEC-2019-179 1.0\nFlask 0.5     PYSEC-2018-66  0.12.3\n  Audit dependencies including descriptions:  $ pip-audit --desc\nFound 2 known vulnerabilities in 1 packages\nName  Version ID             Fix Versions Description\n----  ------- -------------- ------------ --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------   ------------\nFlask 0.5     PYSEC-2019-179 1.0          The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may overlap CVE-2018-1000656.\nFlask 0.5     PYSEC-2018-66  0.12.3       The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3. NOTE: this may overlap CVE-2019-1010083.\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:59.429463Z"}, {"uuid": "966ea8d2-474c-4818-9898-a1df1c1ec2ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://t.me/hacking_Attack/39261", "content": "Audit dependencies in JSON format:  $ pip-audit -f json | jq\nFound 2 known vulnerabilities in 1 packages\n[\n  {\n    \"name\": \"flask\",\n    \"version\": \"0.5\",\n    \"vulns\": [\n      {\n        \"id\": \"PYSEC-2019-179\",\n        \"fix_versions\": [\n          \"1.0\"\n        ],\n        \"description\": \"The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may overlap CVE-2018-1000656.\"\n      },\n      {\n        \"id\": \"PYSEC-2018-66\",\n        \"fix_versions\": [\n          \"0.12.3\"\n        ],\n        \"description\": \"The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vu   lnerability appears to have been fixed in 0.12.3. NOTE: this may overlap CVE-2019-1010083.\"\n      }\n    ]\n  },\n  {\n    \"name\": \"jinja2\",\n    \"version\": \"3.0.2\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"pip\",\n    \"version\": \"21.3.1\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"setuptools\",\n    \"version\": \"57.4.0\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"werkzeug\",\n    \"version\": \"2.0.2\",\n    \"vulns\": []\n  },\n  {\n    \"name\": \"markupsafe\",\n    \"version\": \"2.0.1\",\n    \"vulns\": []\n  }\n]\n  Security Model  This section exists to describe the security assumptions you can and must not  make when using pip-audit.  TL;DR: If you wouldn't pip install it, you should not pip audit it.  pip-audit is a tool for auditing Python environments for packages with  known vulnerabilities. A \"known vulnerability\" is a publicly reported flaw in  a package that, if uncorrected, might allow a malicious actor to perform  unintended actions.  pip-audit can protect you against known vulnerabilities by telling  you when you have them, and how you should upgrade them. For example,  if you have somepackage==1.2.3 in your environment, pip-audit can tell  you that it needs to be upgraded to 1.2.4.  You can assume that pip-audit will make a best effort to fully resolve  all of your Python dependencies and either fully audit each or explicitly  state which ones it has skipped, as well as why it has skipped them.  pip-audit is not a static code analyzer. It analyzes dependency trees,  not code, and it cannot guarantee that arbitrary dependency resolutions  occur statically. To understand why this is, refer to Dustin Ingram's  excellent post on dependency resolution in Python (https://dustingram.com/articles/2018/03/05/why-pypi-doesnt-know-dependencies/).  As such: you must not assume that pip-audit will defend you against  malicious packages. In particular, it is incorrect to treat  pip-audit -r INPUT as a \"more secure\" variant of pip-audit. For all intents  and purposes, pip-audit -r INPUT is functionally equivalent to  pip install -r INPUT, with a small amount of non-security isolation to  avoid conflicts with any of your local environments.  Licensing  pip-audit is licensed under the Apache 2.0 License.  pip-audit reuses and modifies examples from  resolvelib, which is licensed under  the ISC license.  Contributing  See the contributing docs (https://github.com/trailofbits/pip-audit/blob/main/CONTRIBUTING.md) for details.  Code of Conduct  Everyone interacting with this project is expected to follow the  PSF Code of Conduct (https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md).  \n\nDownload Pip-Audit (https://github.com/trailofbits/pip-audit)\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:21.716253Z"}, {"uuid": "ef0d753d-8894-48b0-99b7-bfbef0d33e5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-1010083", "type": "seen", "source": "https://t.me/hacking_Attack/39260", "content": "-f FORMAT, --format FORMAT\n                        the format to emit audit    results in (choices: columns,\n                        json, cyclonedx-json, cyclonedx-xml) (default:\n                        columns)\n  -s SERVICE, --vulnerability-service SERVICE\n                        the vulnerability service to audit dependencies\n                        against (choices: osv, pypi) (default: pypi)\n  -d, --dry-run         collect all dependencies but do not perform the\n                        auditing step (default: False)\n  -S, --strict          fail the entire audit if dependency collection fails\n                        on any dependency (default: False)\n  --desc [{on,off,auto}]\n                        include a description for each vulnerability; `auto`\n                        defaults to `on` for the `json` format. This flag has\n                        no effect on the `cyclonedx-json` or `cyclonedx-xml`\n                        formats. (default: auto)\n  --cache-dir CACHE_DIR\n                           the directory to use as an HTTP cache for PyPI; uses\n                        the `pip` HTTP cache by default (default: None)\n  --progress-spinner {on,off}\n                        display a progress spinner (default: on)\n  --timeout TIMEOUT     set the socket timeout (default: 15)\n  --path PATHS          restrict to the specified installation path for\n                        auditing packages; this option can be used multiple\n                        times (default: [])\n  -v, --verbose         give more output; this setting overrides the\n                        `PIP_AUDIT_LOGLEVEL` variable and is equivalent to\n                        setting it to `debug` (default: False)\n  Exit codes  On completion, pip-audit will exit with a code indicating its status.  The current codes are:    0: No known vulnerabilities (https://www.kitploit.com/search/label/Known%20Vulnerabilities) were detected.  1: One or more known vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) were found.    Examples  Audit dependencies for the current Python environment:  $ pip-audit\nNo known vulnerabilities found\n  Audit dependencies for a given requirements file:  $ pip-audit -r ./requirements.txt\nNo known vulnerabilities found\n  Audit dependencies for the current Python environment excluding system packages:  $ pip-audit -r ./requirements.txt -l\nNo known vulnerabilities found\n  Audit dependencies when there are vulnerabilities present:  $ pip-audit\nFound 2 known vulnerabilities in 1 packages\nName  Version ID             Fix Versions\n----  ------- -------------- ------------\nFlask 0.5     PYSEC-2019-179 1.0\nFlask 0.5     PYSEC-2018-66  0.12.3\n  Audit dependencies including descriptions:  $ pip-audit --desc\nFound 2 known vulnerabilities in 1 packages\nName  Version ID             Fix Versions Description\n----  ------- -------------- ------------ --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------   ------------\nFlask 0.5     PYSEC-2019-179 1.0          The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may overlap CVE-2018-1000656.\nFlask 0.5     PYSEC-2018-66  0.12.3       The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3. NOTE: this may overlap CVE-2019-1010083.\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:21.842785Z"}]}