{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19829 is a medium-severity vulnerability in n/a, published on 18 Dec 2018. 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-2018-19829 and fix it if it is affected.\n\nWhat it is: CVE-2018-19829 is a medium-severity vulnerability in n/a, published on 18 Dec 2018. 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-2018-19829 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-2018-19829/ (Markdown: https://insights.sbomify.com/CVE-2018-19829/index.md)","id":"CVE-2018-19829","markdown":"https://insights.sbomify.com/CVE-2018-19829/index.md","name":"CVE-2018-19829","record":{"aliases":["GHSA-x68j-9482-g532"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Integria IMS","requires_auth":"none","summary":"Attackers can delete arbitrary users in Integria IMS via CSRF if the user ID is known.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"integria_ims","vendor":"artica"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Artica Integria IMS 5.0.83 has CSRF in godmode/usuarios/lista_usuarios, resulting in the ability to delete an arbitrary user when the ID number is known.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-12-19","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-12-19","kind":"exploitdb","ref":"46013","stars":null,"title":"Integria IMS 5.0.83 - Cross-Site Request Forgery"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-19829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-19830"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19828"},"products":["n/a"],"published":"2018-12-18","related":[{"cvss_score":9.8,"headline":"Integria IMS Remote Code Execution","id":"CVE-2021-3832","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":9.8,"headline":"Integria IMS incorrect authorization","id":"CVE-2021-3833","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-15091","kev_date_added":null,"published":"2019-08-16"},{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2018-1000812","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19828","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":5.4,"headline":"Integria IMS vulnerable to Cross Site Scripting (XSS)","id":"CVE-2021-3834","kev_date_added":null,"published":"2021-10-07"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can delete arbitrary users in Integria IMS via CSRF if the user ID is known.","url":"https://insights.sbomify.com/CVE-2018-19829/"}