{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16253 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16253 is a medium-severity vulnerability in n/a, published on 7 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16253 and fix it if it is affected.\n\nWhat it is: CVE-2018-16253 is a medium-severity vulnerability in n/a, published on 7 Nov 2018. 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-2018-16253 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-16253/ (Markdown: https://insights.sbomify.com/CVE-2018-16253/index.md)","id":"CVE-2018-16253","markdown":"https://insights.sbomify.com/CVE-2018-16253/index.md","name":"CVE-2018-16253","record":{"aliases":["GHSA-g43p-7j43-jpj7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TLS library","requires_auth":"none","summary":"Remote attackers can forge X.509 certificates due to improper ASN.1 metadata verification in axTLS, enabling impersonation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"axtls","vendor":"axtls_project"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is an even more permissive variant of CVE-2006-4790 and CVE-2014-1568.","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":"Security feature bypass in n/a","id":"CVE-2018-16253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16254"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2018-16252"},"products":["n/a"],"published":"2018-11-07","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-8981","kev_date_added":null,"published":"2019-03-26"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-10013","kev_date_added":null,"published":"2019-12-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-9689","kev_date_added":null,"published":"2019-12-03"},{"cvss_score":5.9,"headline":"Memory corruption in n/a","id":"CVE-2018-16149","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.9,"headline":"Weak cryptography in n/a","id":"CVE-2018-16150","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2023-33613","kev_date_added":null,"published":"2023-06-06"}],"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":"Remote attackers can forge X.509 certificates due to improper ASN.1 metadata verification in axTLS, enabling impersonation.","url":"https://insights.sbomify.com/CVE-2018-16253/"}