{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-33484 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-33484 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-33484 is a high-severity vulnerability in n/a, published on 7 Sep 2021. 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-33484 and fix it if it is affected.\n\nWhat it is: CVE-2021-33484 is a high-severity vulnerability in n/a, published on 7 Sep 2021. 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-33484 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-2021-33484/ (Markdown: https://insights.sbomify.com/CVE-2021-33484/index.md)","id":"CVE-2021-33484","markdown":"https://insights.sbomify.com/CVE-2021-33484/index.md","name":"CVE-2021-33484","record":{"aliases":["GHSA-76j4-qr57-p9fg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Comments Pro plugin","requires_auth":"none","summary":"Hardcoded encryption IV allows attackers to decrypt keys and spoof user identities in Comments Pro, enabling unauthorized comment posting as other users.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"onyaktech_comments_pro","vendor":"onyaktech_comments_pro_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in CommentsService.ashx in OnyakTech Comments Pro 3.8. An attacker can download a copy of the installer, decompile it, and discover a hardcoded IV used to encrypt the username and userid in the comment POST request. Additionally, the attacker can decrypt the encrypted encryption key (sent as a parameter in the comment form request) by setting this encrypted value as the username, which will appear on the comment page in its decrypted form. Using these two values (combined with the encryption functionality discovered in the decompiled installer), the attacker can encrypt another user's ID and username. These values can be used as part of the comment posting request in order to spoof the user.","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":"Hardcoded credentials in n/a","id":"CVE-2021-33484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-33485"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-33483"},"products":["n/a"],"published":"2021-09-07","related":[{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2021-33483","kev_date_added":null,"published":"2021-09-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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Hardcoded encryption IV allows attackers to decrypt keys and spoof user identities in Comments Pro, enabling unauthorized comment posting as other users.","url":"https://insights.sbomify.com/CVE-2021-33484/"}