[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$feOKFgeagIeCfLM_o0IdQJaZKxgtOrdE35xDtLymNQOE":3,"g5a-ex:fujitsu\u002Fm10-4s_firmware@*":122,"g5a-family:fujitsu\u002Fm10-4s_firmware":124},{"success":4,"data":5},true,{"product":6,"versions":32,"topVulnerabilitiesByEpss":41,"kevVulnerabilities":99,"seoMetadata":100,"meta":119},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":31},"fujitsu","m10-4s_firmware",8,13,0,"2021-02-16",[14,17,19,21,23,25,27,29],{"version":15,"cve_count":11,"kev_count":11,"has_kev":16},"xcp",false,{"version":18,"cve_count":11,"kev_count":11,"has_kev":16},"xcp2280",{"version":20,"cve_count":11,"kev_count":11,"has_kev":16},"xcp2361",{"version":22,"cve_count":11,"kev_count":11,"has_kev":16},"xcp2400",{"version":24,"cve_count":11,"kev_count":11,"has_kev":16},"xcp2410",{"version":26,"cve_count":11,"kev_count":11,"has_kev":16},"xcp3070",{"version":28,"cve_count":11,"kev_count":11,"has_kev":16},"xcp3100",{"version":30,"cve_count":11,"kev_count":11,"has_kev":16},"xcp3110","M10-4s Firmware by Fujitsu is a technology product with 8 tracked versions and 13 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[33,34,35,36,37,38,39,40],{"version":15,"cve_count":11,"kev_count":11,"has_kev":16},{"version":18,"cve_count":11,"kev_count":11,"has_kev":16},{"version":20,"cve_count":11,"kev_count":11,"has_kev":16},{"version":22,"cve_count":11,"kev_count":11,"has_kev":16},{"version":24,"cve_count":11,"kev_count":11,"has_kev":16},{"version":26,"cve_count":11,"kev_count":11,"has_kev":16},{"version":28,"cve_count":11,"kev_count":11,"has_kev":16},{"version":30,"cve_count":11,"kev_count":11,"has_kev":16},[42,50,55,61,66,71,78,85,89,94],{"cveId":43,"description":44,"publishedDate":45,"cvssScore":46,"cvssVersion":47,"severity":48,"isKev":16,"epssScore":49},"CVE-2013-2566","The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for remote attackers to conduct plaintext-recovery attacks via statistical analysis of ciphertext in a large number of sessions that use the same plaintext.","2013-03-15",5.9,"v3.1","Medium",0.84424,{"cveId":51,"description":52,"publishedDate":53,"cvssScore":46,"cvssVersion":47,"severity":48,"isKev":16,"epssScore":54},"CVE-2019-6111","An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files\u002Fdirectories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh\u002Fauthorized_keys file).","2019-01-31",0.58204,{"cveId":56,"description":57,"publishedDate":12,"cvssScore":58,"cvssVersion":47,"severity":59,"isKev":16,"epssScore":60},"CVE-2021-23840","Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).",7.5,"High",0.50732,{"cveId":62,"description":63,"publishedDate":64,"cvssScore":58,"cvssVersion":47,"severity":59,"isKev":16,"epssScore":65},"CVE-2016-8610","A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS\u002FSSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS\u002FSSL server consume an excessive amount of CPU and fail to accept connections from other clients.","2017-11-13",0.39657,{"cveId":67,"description":68,"publishedDate":69,"cvssScore":58,"cvssVersion":47,"severity":59,"isKev":16,"epssScore":70},"CVE-2020-8285","curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.","2020-12-14",0.0977,{"cveId":72,"description":73,"publishedDate":74,"cvssScore":75,"cvssVersion":47,"severity":76,"isKev":16,"epssScore":77},"CVE-2018-1000007","libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.","2018-01-24",9.8,"Critical",0.06578,{"cveId":79,"description":80,"publishedDate":81,"cvssScore":82,"cvssVersion":47,"severity":83,"isKev":16,"epssScore":84},"CVE-2020-1968","The Raccoon attack exploits a flaw in the TLS specification which can lead to an attacker being able to compute the pre-master secret in connections which have used a Diffie-Hellman (DH) based ciphersuite. In such a case this would result in the attacker being able to eavesdrop on all encrypted communications sent over that TLS connection. The attack can only be exploited if an implementation re-uses a DH secret across multiple TLS connections. Note that this issue only impacts DH ciphersuites and not ECDH ciphersuites. This issue affects OpenSSL 1.0.2 which is out of support and no longer receiving public updates. OpenSSL 1.1.1 is not vulnerable to this issue. Fixed in OpenSSL 1.0.2w (Affected 1.0.2-1.0.2v).","2020-09-09",3.7,"Low",0.04903,{"cveId":86,"description":87,"publishedDate":69,"cvssScore":82,"cvssVersion":47,"severity":83,"isKev":16,"epssScore":88},"CVE-2020-8284","A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.",0.03898,{"cveId":90,"description":91,"publishedDate":53,"cvssScore":92,"cvssVersion":47,"severity":48,"isKev":16,"epssScore":93},"CVE-2019-6109","An issue was discovered in OpenSSH 7.9. Due to missing character encoding in the progress display, a malicious server (or Man-in-The-Middle attacker) can employ crafted object names to manipulate the client output, e.g., by using ANSI control codes to hide additional files being transferred. This affects refresh_progress_meter() in progressmeter.c.",6.8,0.03807,{"cveId":95,"description":96,"publishedDate":97,"cvssScore":58,"cvssVersion":47,"severity":59,"isKev":16,"epssScore":98},"CVE-2021-3326","The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid input sequences in the ISO-2022-JP-3 encoding, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.","2021-01-27",0.03779,[],{"title":101,"metaDescription":102,"keywords":103,"structuredData":104},"M10-4s Firmware by Fujitsu - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for M10-4s Firmware by Fujitsu covering 8 versions with 13 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","M10-4s Firmware vulnerabilities, M10-4s Firmware security, M10-4s Firmware CVE, Fujitsu M10-4s Firmware, M10-4s Firmware threat intelligence, Fujitsu security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":105,"@type":106,"name":107,"description":102,"url":108,"manufacturer":109,"applicationCategory":113,"softwareVersion":114,"mainEntity":115},"https:\u002F\u002Fschema.org","SoftwareApplication","M10-4s Firmware","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Ffujitsu\u002Fm10-4s_firmware",{"@type":110,"name":111,"url":112},"Organization","Fujitsu","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Ffujitsu","Security Software","8 versions tracked",{"@type":116,"name":117,"description":118,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","M10-4s Firmware Security Vulnerabilities","Security vulnerabilities affecting M10-4s Firmware by Fujitsu",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":120,"apiVersion":121},"2026-10-17T14:01:18.160Z","3.0",{"rows":123,"total":11,"capped":16,"failed":11},[],[]]