[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flAHNF0TlfhX8CnH8LWuzatLAXa6XWGAFh96OqFn7Ulg":3,"g5a-ex:siemens\u002Fscalance_xf-200ba@*":87,"g5a-family:siemens\u002Fscalance_xf-200ba":89},{"success":4,"data":5},true,{"product":6,"versions":14,"topVulnerabilitiesByEpss":15,"kevVulnerabilities":64,"seoMetadata":65,"meta":84},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":9,"lastCveUpdate":11,"versions":12,"description":13},"siemens","scalance_xf-200ba",0,8,"2022-08-10",[],"Scalance Xf-200ba by Siemens is a technology product and 8 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[],[16,25,32,38,42,47,53,58],{"cveId":17,"description":18,"publishedDate":19,"cvssScore":20,"cvssVersion":21,"severity":22,"isKev":23,"epssScore":24},"CVE-2021-3449","An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).","2021-03-25",5.9,"v3.1","Medium",false,0.63542,{"cveId":26,"description":27,"publishedDate":28,"cvssScore":29,"cvssVersion":21,"severity":30,"isKev":23,"epssScore":31},"CVE-2020-28400","Affected devices contain a vulnerability that allows an unauthenticated attacker to trigger a denial of service condition. The vulnerability can be triggered if a large amount of DCP reset packets are sent to the device.","2021-07-13",7.5,"High",0.01856,{"cveId":33,"description":34,"publishedDate":11,"cvssScore":35,"cvssVersion":21,"severity":36,"isKev":23,"epssScore":37},"CVE-2022-36323","Affected devices do not properly sanitize an input field.  This could allow an authenticated remote attacker with administrative privileges to inject code or spawn a system root shell.",9.1,"Critical",0.01828,{"cveId":39,"description":40,"publishedDate":11,"cvssScore":29,"cvssVersion":21,"severity":30,"isKev":23,"epssScore":41},"CVE-2022-36324","Affected devices do not properly handle the renegotiation of SSL\u002FTLS parameters. This could allow an unauthenticated remote attacker to bypass the TCP brute force prevention and lead to a denial of service condition for the duration of the attack.",0.01744,{"cveId":43,"description":44,"publishedDate":45,"cvssScore":29,"cvssVersion":21,"severity":30,"isKev":23,"epssScore":46},"CVE-2019-13946","Profinet-IO (PNIO) stack versions prior V06.00 do not properly limit\ninternal resource allocation when multiple legitimate diagnostic package\nrequests are sent to the DCE-RPC interface.\nThis could lead to a denial of service condition due to lack of memory\nfor devices that include a vulnerable version of the stack.\n\nThe security vulnerability could be exploited by an attacker with network\naccess to an affected device. Successful exploitation requires no system\nprivileges and no user interaction. An attacker could use the vulnerability\nto compromise the availability of the device.","2020-02-11",0.0146,{"cveId":48,"description":49,"publishedDate":50,"cvssScore":51,"cvssVersion":21,"severity":22,"isKev":23,"epssScore":52},"CVE-2019-10927","A vulnerability has been identified in SCALANCE SC-600 (V2.0), SCALANCE XB-200 (V4.1), SCALANCE XC-200 (V4.1), SCALANCE XF-200BA (V4.1), SCALANCE XP-200 (V4.1), SCALANCE XR-300WG (V4.1). An authenticated attacker with network access to to port 22\u002Ftcp of an affected device may cause a Denial-of-Service condition. The security vulnerability could be exploited by an authenticated attacker with network access to the affected device. No user interaction is required to exploit this vulnerability. The vulnerability impacts the availability of the affected device.","2019-08-13",6.5,0.01168,{"cveId":54,"description":55,"publishedDate":11,"cvssScore":56,"cvssVersion":21,"severity":22,"isKev":23,"epssScore":57},"CVE-2022-36325","Affected devices do not properly sanitize data introduced by an user when rendering the web interface. This could allow an authenticated remote attacker with administrative privileges to inject code and lead to a DOM-based XSS.",4.8,0.00956,{"cveId":59,"description":60,"publishedDate":61,"cvssScore":62,"cvssVersion":21,"severity":30,"isKev":23,"epssScore":63},"CVE-2021-25667","A vulnerability has been identified in RUGGEDCOM RM1224 (All versions >= V4.3 and \u003C V6.4), SCALANCE M-800 (All versions >= V4.3 and \u003C V6.4), SCALANCE S615 (All versions >= V4.3 and \u003C V6.4), SCALANCE SC-600 Family (All versions >= V2.0 and \u003C V2.1.3), SCALANCE XB-200 (All versions \u003C V4.1), SCALANCE XC-200 (All versions \u003C V4.1), SCALANCE XF-200BA (All versions \u003C V4.1), SCALANCE XM400 (All versions \u003C V6.2), SCALANCE XP-200 (All versions \u003C V4.1), SCALANCE XR-300WG (All versions \u003C V4.1), SCALANCE XR500 (All versions \u003C V6.2). Affected devices contain a stack-based buffer overflow vulnerability in the handling of STP BPDU frames that could allow a remote attacker to trigger a denial-of-service condition or potentially remote code execution. Successful exploitation requires the passive listening feature of the device to be active.","2021-03-15",8.8,0.00953,[],{"title":66,"metaDescription":67,"keywords":68,"structuredData":69},"Scalance Xf-200ba by Siemens - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Scalance Xf-200ba by Siemens with 8 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Scalance Xf-200ba vulnerabilities, Scalance Xf-200ba security, Scalance Xf-200ba CVE, Siemens Scalance Xf-200ba, Scalance Xf-200ba threat intelligence, Siemens security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":70,"@type":71,"name":72,"description":67,"url":73,"manufacturer":74,"applicationCategory":78,"softwareVersion":79,"mainEntity":80},"https:\u002F\u002Fschema.org","SoftwareApplication","Scalance Xf-200ba","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Fsiemens\u002Fscalance_xf-200ba",{"@type":75,"name":76,"url":77},"Organization","Siemens","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fsiemens","Security Software","Multiple versions",{"@type":81,"name":82,"description":83,"vulnerabilityCount":10,"dateModified":11},"SecurityVulnerability","Scalance Xf-200ba Security Vulnerabilities","Security vulnerabilities affecting Scalance Xf-200ba by Siemens",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":9,"lastUpdated":11,"generatedAt":85,"apiVersion":86},"2026-10-19T00:58:17.076Z","3.0",{"rows":88,"total":9,"capped":23,"failed":9},[],[90],{"product":91,"cves":10},"scalance_xf-200ba_firmware"]