{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-26948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-26948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-26948 is a medium-severity vulnerability in n/a, published on 29 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-26948 and fix it if it is affected.\n\nWhat it is: CVE-2022-26948 is a medium-severity vulnerability in n/a, published on 29 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-26948 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-2022-26948/ (Markdown: https://insights.sbomify.com/CVE-2022-26948/index.md)","id":"CVE-2022-26948","markdown":"https://insights.sbomify.com/CVE-2022-26948/index.md","name":"CVE-2022-26948","record":{"aliases":["GHSA-hf2v-jxv9-ggj2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Archer RSS integration","requires_auth":"low_privilege","summary":"Attackers can obtain stored credentials from the Archer RSS feed integration, enabling further attacks and potential account takeover.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"archer","vendor":"rsa"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:H/AV:P/A:H/C:H/I:L/PR:L/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"The Archer RSS feed integration for Archer 6.x through 6.9 SP1 (6.9.1.0) is affected by an insecure credential storage vulnerability. A malicious attacker may obtain access to credential information to use it in further attacks.","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-2022-26948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-26949"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-26947"},"products":["n/a"],"published":"2022-03-29","related":[{"cvss_score":9.6,"headline":"Missing authorization in n/a","id":"CVE-2022-30584","kev_date_added":null,"published":"2022-05-26"},{"cvss_score":8.8,"headline":"Information disclosure in RSA Archer","id":"CVE-2020-5331","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":8.8,"headline":"Privilege escalation in RSA Archer","id":"CVE-2018-11060","kev_date_added":null,"published":"2018-07-24"},{"cvss_score":8.2,"headline":"Cross-site scripting in RSA Archer","id":"CVE-2020-5334","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":8.2,"headline":"Cross-site scripting in RSA Archer","id":"CVE-2018-11059","kev_date_added":null,"published":"2018-07-24"},{"cvss_score":8.1,"headline":"Auth bypass in RSA Archer","id":"CVE-2019-3758","kev_date_added":null,"published":"2019-09-18"},{"cvss_score":7.6,"headline":"Cross-site scripting in n/a","id":"CVE-2022-37317","kev_date_added":null,"published":"2022-08-25"}],"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":"Attackers can obtain stored credentials from the Archer RSS feed integration, enabling further attacks and potential account takeover.","url":"https://insights.sbomify.com/CVE-2022-26948/"}