{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-4031 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-4031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-4031 is a high-severity vulnerability in Syltek, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-4031 and fix it if it is affected.\n\nWhat it is: CVE-2021-4031 is a high-severity vulnerability in Syltek, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-4031 in the wild and no public exploit code.\n\nAffected product: Syltek. 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-2021-4031/ (Markdown: https://insights.sbomify.com/CVE-2021-4031/index.md)","id":"CVE-2021-4031","markdown":"https://insights.sbomify.com/CVE-2021-4031/index.md","name":"CVE-2021-4031","record":{"aliases":["GHSA-v62q-78f9-67xv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Syltek application","requires_auth":"none","summary":"Attackers can bypass payment verification by forging requests to mark items as paid without valid payment, affecting Syltek application users.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"syltek","vendor":"syltek"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Syltek application before its 10.22.00 version, does not correctly check that a product ID has a valid payment associated to it. This could allow an attacker to forge a request and bypass the payment system by marking items as payed without any verification.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Syltek Insufficient Verification of Data Authenticity","id":"CVE-2021-4031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in kernel","id":"CVE-2021-4032"},"packages":[],"prev":{"headline":"Cross-site request forgery in ARMOR Z1 (NBG6816) firmware","id":"CVE-2021-4030"},"products":["Syltek"],"published":"2022-03-18","related":[],"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-09-16","vendors":["Syltek"]},"summary":"Attackers can bypass payment verification by forging requests to mark items as paid without valid payment, affecting Syltek application users.","url":"https://insights.sbomify.com/CVE-2021-4031/"}