[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvsOBNLJ6eWn1yQdHr3rDC25mr7WdZjA5XFYgqazNbVM":3,"g5a-ex:oracle\u002Fmysql_workbench@*":171,"g5a-family:oracle\u002Fmysql_workbench":173},{"success":4,"data":5},true,{"product":6,"versions":62,"topVulnerabilitiesByEpss":86,"kevVulnerabilities":148,"seoMetadata":149,"meta":168},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":61},"oracle","mysql_workbench",23,42,0,"2022-05-03",[14,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59],{"version":15,"cve_count":11,"kev_count":11,"has_kev":16},"5.2.47",false,{"version":18,"cve_count":11,"kev_count":11,"has_kev":16},"6.0.9",{"version":20,"cve_count":11,"kev_count":11,"has_kev":16},"6.1.7",{"version":22,"cve_count":11,"kev_count":11,"has_kev":16},"6.2.5",{"version":24,"cve_count":11,"kev_count":11,"has_kev":16},"6.3.10",{"version":26,"cve_count":11,"kev_count":11,"has_kev":16},"6.3.8",{"version":28,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.12",{"version":30,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.13",{"version":32,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.14",{"version":34,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.15",{"version":36,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.16",{"version":38,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.17",{"version":40,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.18",{"version":42,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.19",{"version":44,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.20",{"version":46,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.21",{"version":48,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.22",{"version":50,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.23",{"version":52,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.24",{"version":54,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.25",{"version":56,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.26",{"version":58,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.27",{"version":60,"cve_count":11,"kev_count":11,"has_kev":16},"8.0.29","Mysql Workbench by Oracle is a technology product with 23 tracked versions and 42 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85],{"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},{"version":32,"cve_count":11,"kev_count":11,"has_kev":16},{"version":34,"cve_count":11,"kev_count":11,"has_kev":16},{"version":36,"cve_count":11,"kev_count":11,"has_kev":16},{"version":38,"cve_count":11,"kev_count":11,"has_kev":16},{"version":40,"cve_count":11,"kev_count":11,"has_kev":16},{"version":42,"cve_count":11,"kev_count":11,"has_kev":16},{"version":44,"cve_count":11,"kev_count":11,"has_kev":16},{"version":46,"cve_count":11,"kev_count":11,"has_kev":16},{"version":48,"cve_count":11,"kev_count":11,"has_kev":16},{"version":50,"cve_count":11,"kev_count":11,"has_kev":16},{"version":52,"cve_count":11,"kev_count":11,"has_kev":16},{"version":54,"cve_count":11,"kev_count":11,"has_kev":16},{"version":56,"cve_count":11,"kev_count":11,"has_kev":16},{"version":58,"cve_count":11,"kev_count":11,"has_kev":16},{"version":60,"cve_count":11,"kev_count":11,"has_kev":16},[87,95,102,109,115,121,127,133,137,142],{"cveId":88,"description":89,"publishedDate":90,"cvssScore":91,"cvssVersion":92,"severity":93,"isKev":16,"epssScore":94},"CVE-2018-10933","A vulnerability was found in libssh's server-side state machine before versions 0.7.6 and 0.8.4. A malicious client could create channels without first performing authentication, resulting in unauthorized access.","2018-10-17",9.1,"v3.0","Critical",0.91789,{"cveId":96,"description":97,"publishedDate":12,"cvssScore":98,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":101},"CVE-2022-1292","The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).",7.3,"v3.1","High",0.82612,{"cveId":103,"description":104,"publishedDate":105,"cvssScore":106,"cvssVersion":99,"severity":107,"isKev":16,"epssScore":108},"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":110,"description":111,"publishedDate":112,"cvssScore":113,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":114},"CVE-2020-1967","Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the \"signature_algorithms_cert\" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).","2020-04-21",7.5,0.53336,{"cveId":116,"description":117,"publishedDate":118,"cvssScore":119,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":120},"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":122,"description":123,"publishedDate":124,"cvssScore":125,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":126},"CVE-2021-3518","There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.","2021-05-18",8.8,0.21859,{"cveId":128,"description":129,"publishedDate":130,"cvssScore":131,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":132},"CVE-2022-21824","Due to the formatting logic of the \"console.table()\" function it was not safe to allow user controlled input to be passed to the \"properties\" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be \"__proto__\". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object these properties are being assigned to.","2022-02-24",8.2,0.21514,{"cveId":134,"description":135,"publishedDate":105,"cvssScore":119,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":136},"CVE-2021-3450","The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer 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.1h-1.1.1j).",0.18339,{"cveId":138,"description":139,"publishedDate":140,"cvssScore":106,"cvssVersion":99,"severity":107,"isKev":16,"epssScore":141},"CVE-2019-1559","If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable \"non-stitched\" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).","2019-02-27",0.17139,{"cveId":143,"description":144,"publishedDate":145,"cvssScore":146,"cvssVersion":99,"severity":100,"isKev":16,"epssScore":147},"CVE-2021-3517","There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.","2021-05-19",8.6,0.16986,[],{"title":150,"metaDescription":151,"keywords":152,"structuredData":153},"Mysql Workbench by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Mysql Workbench by Oracle covering 23 versions with 42 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Mysql Workbench vulnerabilities, Mysql Workbench security, Mysql Workbench CVE, Oracle Mysql Workbench, Mysql Workbench threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":154,"@type":155,"name":156,"description":151,"url":157,"manufacturer":158,"applicationCategory":162,"softwareVersion":163,"mainEntity":164},"https:\u002F\u002Fschema.org","SoftwareApplication","Mysql Workbench","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fmysql_workbench",{"@type":159,"name":160,"url":161},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","23 versions tracked",{"@type":165,"name":166,"description":167,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Mysql Workbench Security Vulnerabilities","Security vulnerabilities affecting Mysql Workbench by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":169,"apiVersion":170},"2026-10-17T13:01:10.160Z","3.0",{"rows":172,"total":11,"capped":16,"failed":11},[],[]]