{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19930 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19930 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19930 is a medium-severity vulnerability in n/a, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-19930 and fix it if it is affected.\n\nWhat it is: CVE-2019-19930 is a medium-severity vulnerability in n/a, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-19930 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-19930/ (Markdown: https://insights.sbomify.com/CVE-2019-19930/index.md)","id":"CVE-2019-19930","markdown":"https://insights.sbomify.com/CVE-2019-19930/index.md","name":"CVE-2019-19930","record":{"aliases":["GHSA-82ch-g5h5-7x39"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IEC 61850 library","requires_auth":"none","summary":"An integer signedness error in libIEC61850 allows attackers to trigger excessive memory allocation, potentially causing a denial of service.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libiec61850","vendor":"mz-automation"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"In libIEC61850 1.4.0, MmsValue_newOctetString in mms/iso_mms/common/mms_value.c has an integer signedness error that can lead to an attempted excessive memory allocation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Integer overflow in n/a","id":"CVE-2019-19930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-19931"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-19929"},"products":["n/a"],"published":"2019-12-23","related":[{"cvss_score":10,"headline":"MZ Automation libIEC61850 Stack-Based Buffer Overflow","id":"CVE-2022-2970","kev_date_added":null,"published":"2022-09-23"},{"cvss_score":10,"headline":"MZ Automation libIEC61850 Stack-Based Buffer Overflow","id":"CVE-2022-2972","kev_date_added":null,"published":"2022-09-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45970","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45971","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-19185","kev_date_added":null,"published":"2018-11-12"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-18957","kev_date_added":null,"published":"2018-11-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-18834","kev_date_added":null,"published":"2018-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An integer signedness error in libIEC61850 allows attackers to trigger excessive memory allocation, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2019-19930/"}