{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7047 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7047 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7047 is a critical vulnerability in n/a, published on 1 Mar 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-7047 and fix it if it is affected.\n\nWhat it is: CVE-2018-7047 is a critical vulnerability in n/a, published on 1 Mar 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-7047 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-7047/ (Markdown: https://insights.sbomify.com/CVE-2018-7047/index.md)","id":"CVE-2018-7047","markdown":"https://insights.sbomify.com/CVE-2018-7047/index.md","name":"CVE-2018-7047","record":{"aliases":["GHSA-rcrp-hqvr-vx5g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Wowza Streaming Engine","requires_auth":"none","summary":"Attackers can exploit default JMX credentials in Wowza Streaming Engine to read/write files and potentially execute remote code.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"streaming_engine","vendor":"wowza"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in the MBeans Server in Wowza Streaming Engine before 4.7.1. The file system may be read and written to via JMX using the default JMX credentials (remote code execution may be possible as well).","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-2018-7047","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-7048"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-7046"},"products":["n/a"],"published":"2018-03-01","related":[{"cvss_score":9.4,"headline":"Stream Target Remote Code Execution in Wowza Streaming Engine","id":"CVE-2024-52052","kev_date_added":null,"published":"2024-11-21"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2018-19365","kev_date_added":null,"published":"2019-03-18"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2020-9004","kev_date_added":null,"published":"2020-04-14"},{"cvss_score":8.7,"headline":"Wowza Streaming Engine 4.5.0 Privilege Escalation via user edit","id":"CVE-2016-20034","kev_date_added":null,"published":"2026-03-15"},{"cvss_score":8.7,"headline":"Stored Cross-Site Scripting in Wowza Streaming Engine","id":"CVE-2024-52053","kev_date_added":null,"published":"2024-11-21"},{"cvss_score":8.5,"headline":"Wowza Streaming Engine 4.5.0 Local Privilege Escalation via nssm_x64.exe","id":"CVE-2016-20033","kev_date_added":null,"published":"2026-03-15"}],"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":"Attackers can exploit default JMX credentials in Wowza Streaming Engine to read/write files and potentially execute remote code.","url":"https://insights.sbomify.com/CVE-2018-7047/"}