CWE-295
AllowedImproper Certificate Validation
Abstraction: Base · Status: Draft
The product does not validate, or incorrectly validates, a certificate.
2114 vulnerabilities reference this CWE, most recent first.
GHSA-CM7J-P8HC-97VJ
Vulnerability from github – Published: 2022-07-28 00:00 – Updated: 2022-12-12 20:36Jenkins Git client plugin 3.11.0 and earlier does not perform SSH host key verification when connecting to Git repositories via SSH, enabling man-in-the-middle attacks. Git client Plugin 3.11.1 provides strategies for performing host key verification for administrators to select the one that meets their security needs. For more information see the plugin documentation.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.11.0"
},
"package": {
"ecosystem": "Maven",
"name": "org.jenkins-ci.plugins:git-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.11.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-36881"
],
"database_specific": {
"cwe_ids": [
"CWE-295",
"CWE-322"
],
"github_reviewed": true,
"github_reviewed_at": "2022-08-10T17:39:44Z",
"nvd_published_at": "2022-07-27T15:15:00Z",
"severity": "MODERATE"
},
"details": "Jenkins Git client plugin 3.11.0 and earlier does not perform SSH host key verification when connecting to Git repositories via SSH, enabling man-in-the-middle attacks. Git client Plugin 3.11.1 provides strategies for performing host key verification for administrators to select the one that meets their security needs. For more information see [the plugin documentation](https://github.com/jenkinsci/git-client-plugin#ssh-host-key-verification).",
"id": "GHSA-cm7j-p8hc-97vj",
"modified": "2022-12-12T20:36:46Z",
"published": "2022-07-28T00:00:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-36881"
},
{
"type": "WEB",
"url": "https://github.com/jenkinsci/git-client-plugin/commit/88f52c6c9b18bca4ad210e3b9910a49433583fd9"
},
{
"type": "PACKAGE",
"url": "https://github.com/jenkinsci/git-client-plugin"
},
{
"type": "WEB",
"url": "https://www.jenkins.io/security/advisory/2022-07-27/#SECURITY-1468"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2022/07/27/1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Jenkins Git client plugin 3.11.0 does not perform SSH host key verification"
}
GHSA-CM9H-VV4M-6MWP
Vulnerability from github – Published: 2022-05-13 01:24 – Updated: 2025-04-20 03:39The "Community State Bank - Lamar Mobile Banking" by Community State Bank - Lamar app 3.0.3 -- aka community-state-bank-lamar-mobile-banking/id1083927885 for iOS does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
{
"affected": [],
"aliases": [
"CVE-2017-9585"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-06-16T12:29:00Z",
"severity": "MODERATE"
},
"details": "The \"Community State Bank - Lamar Mobile Banking\" by Community State Bank - Lamar app 3.0.3 -- aka community-state-bank-lamar-mobile-banking/id1083927885 for iOS does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.",
"id": "GHSA-cm9h-vv4m-6mwp",
"modified": "2025-04-20T03:39:13Z",
"published": "2022-05-13T01:24:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-9585"
},
{
"type": "WEB",
"url": "https://medium.com/%40chronic_9612/advisory-44-credit-union-apps-for-ios-may-allow-login-credential-exposure-4d2f380b85c5"
},
{
"type": "WEB",
"url": "https://medium.com/@chronic_9612/advisory-44-credit-union-apps-for-ios-may-allow-login-credential-exposure-4d2f380b85c5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CPWQ-8448-9QV3
Vulnerability from github – Published: 2026-03-18 21:32 – Updated: 2026-03-18 21:32Improper certificate validation in Devolutions Hub Reporting Service 2025.3.1.1 and earlier allows a network attacker to perform a man-in-the-middle attack via disabled TLS certificate verification.
{
"affected": [],
"aliases": [
"CVE-2026-4396"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-18T20:16:22Z",
"severity": "HIGH"
},
"details": "Improper certificate validation in Devolutions Hub Reporting Service \n2025.3.1.1 and earlier allows a network attacker to perform a \nman-in-the-middle attack via disabled TLS certificate verification.",
"id": "GHSA-cpwq-8448-9qv3",
"modified": "2026-03-18T21:32:59Z",
"published": "2026-03-18T21:32:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-4396"
},
{
"type": "WEB",
"url": "https://devolutions.net/security/advisories/DEVO-2026-0009"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-CQ39-26J4-6JCJ
Vulnerability from github – Published: 2022-05-13 01:04 – Updated: 2022-05-13 01:04The Siemens SIMATIC S7-1200 2.x PLC does not properly protect the private key of the SIMATIC CONTROLLER Certification Authority certificate, which allows remote attackers to spoof the S7-1200 web server by using this key to create a forged certificate.
{
"affected": [],
"aliases": [
"CVE-2012-3037"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-09-25T11:07:00Z",
"severity": "MODERATE"
},
"details": "The Siemens SIMATIC S7-1200 2.x PLC does not properly protect the private key of the SIMATIC CONTROLLER Certification Authority certificate, which allows remote attackers to spoof the S7-1200 web server by using this key to create a forged certificate.",
"id": "GHSA-cq39-26j4-6jcj",
"modified": "2022-05-13T01:04:09Z",
"published": "2022-05-13T01:04:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-3037"
},
{
"type": "WEB",
"url": "http://en.securitylab.ru/lab/PT-2012-48"
},
{
"type": "WEB",
"url": "http://www.siemens.com/corporate-technology/pool/de/forschungsfelder/siemens_security_advisory_ssa-240718.pdf"
},
{
"type": "WEB",
"url": "http://www.us-cert.gov/control_systems/pdf/ICSA-12-263-01.pdf"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-CQHC-2H57-WPXF
Vulnerability from github – Published: 2026-08-28 19:03 – Updated: 2026-08-28 19:03Summary
When SSL/TLS is enabled but no CA / server certificate is provided, the connector verifies the server's identity using fingerprint validation. The check is effective, the connection is ultimately rejected when it fails, but it happens after the authentication exchange. As a result, the credentials are sent before validation occurs, so an active man-in-the-middle who presents their own certificate receives the password in the handshake before the connection is aborted.
Impact
The credentials are transmitted to the peer before the server's identity is validated. An on-path attacker (MitM) presenting any certificate can capture the account password, even though the connection then fails the fingerprint check and is closed. The disclosed credentials can subsequently be used to authenticate directly against the server.
- Attacker requirement: active man-in-the-middle position on the network path
- Affected configuration: SSL/TLS enabled without a CA / server certificate
Affected versions
- < 3.2.4
- 3.3.0 – 3.3.2
- 3.4.0 – 3.4.5
- 3.5.0 – 3.5.2
Patches
Fixed in 3.2.4, 3.3.3, 3.4.6, and 3.5.3. Upgrade to one of these (or later) on your branch.
Workarounds
Until you can upgrade, configure certificate verification explicitly, provide the server/CA certificate and use a verifying SSL mode (e.g. VERIFY_CA / VERIFY_FULL).
Reported by haaahaaahiihiiii (no GitHub account).
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "mariadb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "mariadb"
},
"ranges": [
{
"events": [
{
"introduced": "3.3.0"
},
{
"fixed": "3.3.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "mariadb"
},
"ranges": [
{
"events": [
{
"introduced": "3.4.0"
},
{
"fixed": "3.4.6"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "mariadb"
},
"ranges": [
{
"events": [
{
"introduced": "3.5.0"
},
{
"fixed": "3.5.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-55215"
],
"database_specific": {
"cwe_ids": [
"CWE-295",
"CWE-522"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-28T19:03:38Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary\nWhen SSL/TLS is enabled but no CA / server certificate is provided, the\nconnector verifies the server\u0027s identity using fingerprint validation. The\ncheck is effective, the connection is ultimately rejected when it fails, \nbut it happens *after* the authentication exchange. As a result, the\ncredentials are sent before validation occurs, so an active man-in-the-middle\nwho presents their own certificate receives the password in the handshake\nbefore the connection is aborted.\n\n### Impact\nThe credentials are transmitted to the peer before the server\u0027s identity is\nvalidated. An on-path attacker (MitM) presenting any certificate can capture\nthe account password, even though the connection then fails the fingerprint\ncheck and is closed. The disclosed credentials can subsequently be used to\nauthenticate directly against the server.\n\n- Attacker requirement: active man-in-the-middle position on the network path\n- Affected configuration: SSL/TLS enabled without a CA / server certificate\n\n### Affected versions\n- \u003c 3.2.4\n- 3.3.0 \u2013 3.3.2\n- 3.4.0 \u2013 3.4.5\n- 3.5.0 \u2013 3.5.2\n\n### Patches\nFixed in 3.2.4, 3.3.3, 3.4.6, and 3.5.3. Upgrade to one of these (or later)\non your branch.\n\n### Workarounds\nUntil you can upgrade, configure certificate verification explicitly, provide\nthe server/CA certificate and use a verifying SSL mode (e.g. VERIFY_CA /\nVERIFY_FULL). \n\nReported by haaahaaahiihiiii (no GitHub account).",
"id": "GHSA-cqhc-2h57-wpxf",
"modified": "2026-08-28T19:03:38Z",
"published": "2026-08-28T19:03:38Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cqhc-2h57-wpxf"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/514576a5a1fab3ea8498613e259a0b7a764e7302"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/c47d7275835c78c7eb8186cd23e9d57c045c128b"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/ecd36958e6e3bf0e0fa8389546f50c0ed6dbb2ac"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3777370"
},
{
"type": "PACKAGE",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6"
},
{
"type": "WEB",
"url": "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3"
},
{
"type": "WEB",
"url": "https://jira.mariadb.org/browse/CONJS-349"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "MariaDB\u0027s connector leaks the cleartext password to an MitM despite `ssl: true`"
}
GHSA-CR54-4MF7-RG5V
Vulnerability from github – Published: 2024-09-05 21:31 – Updated: 2024-09-19 18:30An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert).
{
"affected": [],
"aliases": [
"CVE-2024-45159"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-09-05T19:15:13Z",
"severity": "CRITICAL"
},
"details": "An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert).",
"id": "GHSA-cr54-4mf7-rg5v",
"modified": "2024-09-19T18:30:51Z",
"published": "2024-09-05T21:31:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45159"
},
{
"type": "WEB",
"url": "https://github.com/Mbed-TLS/mbedtls/releases"
},
{
"type": "WEB",
"url": "https://mbed-tls.readthedocs.io/en/latest/security-advisories"
},
{
"type": "WEB",
"url": "https://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2024-08-3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-CRQH-WR78-6JGR
Vulnerability from github – Published: 2023-01-27 06:30 – Updated: 2023-02-06 21:30In Apache::Session::Browseable before 1.3.6, validity of the X.509 certificate is not checked by default when connecting to remote LDAP backends, because the default configuration of the Net::LDAPS module for Perl is used. NOTE: this can, for example, be fixed in conjunction with the CVE-2020-16093 fix.
{
"affected": [],
"aliases": [
"CVE-2020-36659"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-01-27T05:15:00Z",
"severity": "HIGH"
},
"details": "In Apache::Session::Browseable before 1.3.6, validity of the X.509 certificate is not checked by default when connecting to remote LDAP backends, because the default configuration of the Net::LDAPS module for Perl is used. NOTE: this can, for example, be fixed in conjunction with the CVE-2020-16093 fix.",
"id": "GHSA-crqh-wr78-6jgr",
"modified": "2023-02-06T21:30:33Z",
"published": "2023-01-27T06:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-36659"
},
{
"type": "WEB",
"url": "https://github.com/LemonLDAPNG/Apache-Session-Browseable/commit/fdf393235140b293cae5578ef136055a78f3574f"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2023/01/msg00025.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-CVCP-P7F2-2RHW
Vulnerability from github – Published: 2024-07-11 15:30 – Updated: 2024-07-11 15:30The TLS certificate validation code is flawed. An attacker can obtain a TLS certificate from the Stork server and use it to connect to the Stork agent. Once this connection is established with the valid certificate, the attacker can send malicious commands to a monitored service (Kea or BIND 9), possibly resulting in confidential data loss and/or denial of service. It should be noted that this vulnerability is not related to BIND 9 or Kea directly, and only customers using the Stork management tool are potentially affected. This issue affects Stork versions 0.15.0 through 1.15.0.
{
"affected": [],
"aliases": [
"CVE-2024-28872"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-11T15:15:11Z",
"severity": "HIGH"
},
"details": "The TLS certificate validation code is flawed. An attacker can obtain a TLS certificate from the Stork server and use it to connect to the Stork agent. Once this connection is established with the valid certificate, the attacker can send malicious commands to a monitored service (Kea or BIND 9), possibly resulting in confidential data loss and/or denial of service. It should be noted that this vulnerability is not related to BIND 9 or Kea directly, and only customers using the Stork management tool are potentially affected.\nThis issue affects Stork versions 0.15.0 through 1.15.0.",
"id": "GHSA-cvcp-p7f2-2rhw",
"modified": "2024-07-11T15:30:51Z",
"published": "2024-07-11T15:30:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-28872"
},
{
"type": "WEB",
"url": "https://kb.isc.org/docs/cve-2024-28872"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-CW23-WC53-WQ74
Vulnerability from github – Published: 2022-04-23 00:03 – Updated: 2022-05-10 00:00Versions of Motorola Ready For and Motorola Device Help Android applications prior to 2021-04-08 do not properly verify the server certificate which could lead to the communication channel being accessible by an attacker.
{
"affected": [],
"aliases": [
"CVE-2021-3898"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-22T21:15:00Z",
"severity": "MODERATE"
},
"details": "Versions of Motorola Ready For and Motorola Device Help Android applications prior to 2021-04-08 do not properly verify the server certificate which could lead to the communication channel being accessible by an attacker.",
"id": "GHSA-cw23-wc53-wq74",
"modified": "2022-05-10T00:00:44Z",
"published": "2022-04-23T00:03:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3898"
},
{
"type": "WEB",
"url": "https://support.lenovo.com/us/en/product_security/LEN-58311"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CW3V-X7MW-WFCJ
Vulnerability from github – Published: 2025-10-15 21:31 – Updated: 2025-10-15 21:31Improper certificate validation when connecting to gateways in Devolutions Server 2025.3.2 and earlier allows attackers in MitM position to intercept traffic.
{
"affected": [],
"aliases": [
"CVE-2025-11619"
],
"database_specific": {
"cwe_ids": [
"CWE-295"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-10-15T20:15:34Z",
"severity": "HIGH"
},
"details": "Improper certificate validation when connecting to gateways in Devolutions Server 2025.3.2 and earlier allows attackers\u00a0in MitM position to intercept traffic.",
"id": "GHSA-cw3v-x7mw-wfcj",
"modified": "2025-10-15T21:31:40Z",
"published": "2025-10-15T21:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11619"
},
{
"type": "WEB",
"url": "https://devolutions.net/security/advisories/DEVO-2025-0014"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Mitigation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
CAPEC-459: Creating a Rogue Certification Authority Certificate
An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
CAPEC-475: Signature Spoofing by Improper Validation
An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.