[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fNtFNGb3pHj8qT8Lbpft1dujcTifYkVKHWBZXPxe2LH4":3,"g5a-ex:siemens\u002Fsinec_infrastructure_network_services@*":107,"g5a-family:siemens\u002Fsinec_infrastructure_network_services":109},{"success":4,"data":5},true,{"product":6,"versions":21,"topVulnerabilitiesByEpss":24,"kevVulnerabilities":84,"seoMetadata":85,"meta":104},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":20},"siemens","sinec_infrastructure_network_services",2,68,0,"2021-11-23",[14,18],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},"1.0.1",1,false,{"version":19,"cve_count":16,"kev_count":11,"has_kev":17},"1.0.1.1","Sinec Infrastructure Network Services by Siemens is a technology product with 2 tracked versions and 68 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[22,23],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},{"version":19,"cve_count":16,"kev_count":11,"has_kev":17},[25,33,40,45,51,58,63,69,73,78],{"cveId":26,"description":27,"publishedDate":28,"cvssScore":29,"cvssVersion":30,"severity":31,"isKev":17,"epssScore":32},"CVE-2021-25216","In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for 32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly also to achieve remote code execution. We have determined that standard SPNEGO implementations are available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems, rendering the ISC implementation unnecessary and obsolete. Therefore, to reduce the attack surface for BIND users, we will be removing the ISC SPNEGO implementation in the April releases of BIND 9.11 and 9.16 (it had already been dropped from BIND 9.17). We would not normally remove something from a stable ESV (Extended Support Version) of BIND, but since system libraries can replace the ISC SPNEGO implementation, we have made an exception in this case for reasons of stability and security.","2021-04-29",9.8,"v3.1","Critical",0.82367,{"cveId":34,"description":35,"publishedDate":36,"cvssScore":37,"cvssVersion":30,"severity":38,"isKev":17,"epssScore":39},"CVE-2021-22883","Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established. This leads to a leak of file descriptors. If a file descriptor limit is configured on the system, then the server is unable to accept new connections and prevent the process also from opening, e.g. a file. If no file descriptor limit is configured, then this lead to an excessive memory usage and cause the system to run out of memory.","2021-03-03",7.5,"High",0.77385,{"cveId":41,"description":42,"publishedDate":43,"cvssScore":29,"cvssVersion":30,"severity":31,"isKev":17,"epssScore":44},"CVE-2020-7774","The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.","2020-11-17",0.69377,{"cveId":46,"description":47,"publishedDate":48,"cvssScore":49,"cvssVersion":30,"severity":38,"isKev":17,"epssScore":50},"CVE-2020-8625","BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting valid values for the tkey-gssapi-keytab or tkey-gssapi-credentialconfiguration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. The most likely outcome of a successful exploitation of the vulnerability is a crash of the named process. However, remote code execution, while unproven, is theoretically possible. Affects: BIND 9.5.0 -> 9.11.27, 9.12.0 -> 9.16.11, and versions BIND 9.11.3-S1 -> 9.11.27-S1 and 9.16.8-S1 -> 9.16.11-S1 of BIND Supported Preview Edition. Also release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch","2021-02-17",8.1,0.64161,{"cveId":52,"description":53,"publishedDate":54,"cvssScore":55,"cvssVersion":30,"severity":56,"isKev":17,"epssScore":57},"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,"Medium",0.63542,{"cveId":59,"description":60,"publishedDate":61,"cvssScore":49,"cvssVersion":30,"severity":38,"isKev":17,"epssScore":62},"CVE-2021-22901","curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP\u002F1.1 connection or multiplexed HTTP\u002F2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.","2021-06-11",0.63531,{"cveId":64,"description":65,"publishedDate":66,"cvssScore":67,"cvssVersion":30,"severity":38,"isKev":17,"epssScore":68},"CVE-2021-3712","ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own \"d2i\" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the \"data\" and \"length\" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the \"data\" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).","2021-08-24",7.4,0.50445,{"cveId":70,"description":71,"publishedDate":36,"cvssScore":37,"cvssVersion":30,"severity":38,"isKev":17,"epssScore":72},"CVE-2021-22884","Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”. When “localhost6” is not present in \u002Fetc\u002Fhosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160.",0.36842,{"cveId":74,"description":75,"publishedDate":76,"cvssScore":29,"cvssVersion":30,"severity":31,"isKev":17,"epssScore":77},"CVE-2021-22930","Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.","2021-10-07",0.36453,{"cveId":79,"description":80,"publishedDate":81,"cvssScore":82,"cvssVersion":30,"severity":31,"isKev":17,"epssScore":83},"CVE-2021-20093","A buffer over-read vulnerability exists in Wibu-Systems CodeMeter versions \u003C 7.21a. An unauthenticated remote attacker can exploit this issue to disclose heap memory contents or crash the CodeMeter Runtime Server.","2021-06-16",9.1,0.33304,[],{"title":86,"metaDescription":87,"keywords":88,"structuredData":89},"Sinec Infrastructure Network Services by Siemens - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Sinec Infrastructure Network Services by Siemens covering 2 versions with 68 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Sinec Infrastructure Network Services vulnerabilities, Sinec Infrastructure Network Services security, Sinec Infrastructure Network Services CVE, Siemens Sinec Infrastructure Network Services, Sinec Infrastructure Network Services threat intelligence, Siemens security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":90,"@type":91,"name":92,"description":87,"url":93,"manufacturer":94,"applicationCategory":98,"softwareVersion":99,"mainEntity":100},"https:\u002F\u002Fschema.org","SoftwareApplication","Sinec Infrastructure Network Services","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Fsiemens\u002Fsinec_infrastructure_network_services",{"@type":95,"name":96,"url":97},"Organization","Siemens","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fsiemens","Security Software","2 versions tracked",{"@type":101,"name":102,"description":103,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Sinec Infrastructure Network Services Security Vulnerabilities","Security vulnerabilities affecting Sinec Infrastructure Network Services by Siemens",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":105,"apiVersion":106},"2026-10-17T12:38:26.128Z","3.0",{"rows":108,"total":11,"capped":17,"failed":11},[],[]]