Vulnerabilities (CVE)

Filtered by CWE-295
Total 1441 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2016-2402 1 Squareup 2 Okhttp, Okhttp3 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
OkHttp before 2.7.4 and 3.x before 3.1.2 allows man-in-the-middle attackers to bypass certificate pinning by sending a certificate chain with a certificate from a non-pinned trusted CA and the pinned certificate.
CVE-2016-20011 1 Gnome 1 Libgrss 2026-06-17 5.0 MEDIUM 7.5 HIGH
libgrss through 0.7.0 fails to perform TLS certificate verification when downloading feeds, allowing remote attackers to manipulate the contents of feeds without detection. This occurs because of the default behavior of SoupSessionSync.
CVE-2016-1519 1 Grandstream 1 Wave 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
The com.softphone.common package in the Grandstream Wave app 1.0.1.26 and earlier for Android does not properly validate SSL certificates, which allows man-in-the-middle attackers to spoof the Grandstream provisioning server via a crafted certificate.
CVE-2016-1252 2 Canonical, Debian 3 Ubuntu Linux, Advanced Package Tool, Debian Linux 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
The apt package in Debian jessie before 1.0.9.8.4, in Debian unstable before 1.4~beta2, in Ubuntu 14.04 LTS before 1.0.1ubuntu2.17, in Ubuntu 16.04 LTS before 1.2.15ubuntu0.2, and in Ubuntu 16.10 before 1.3.2ubuntu0.1 allows man-in-the-middle attackers to bypass a repository-signing protection mechanism by leveraging improper error handling when validating InRelease file signatures.
CVE-2016-1221 1 Jetstar 1 Jetstar 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
Jetstar App for iOS before 3.0.0 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.
CVE-2016-1210 1 The Hyakugo Bank 1 105 Bank 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
The 105 BANK app 1.0 and 1.1 for Android and 1.0 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.
CVE-2016-1198 1 Ntt 1 Photopt 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
Photopt for Android before 2.0.1 does not verify SSL certificates.
CVE-2016-1186 1 Cybozu 1 Kintone 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
Kintone mobile for Android 1.0.0 through 1.0.5 does not verify SSL server certificates.
CVE-2016-1184 1 Tokyostarbank 1 Tokyo Star Bank 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
Tokyo Star bank App for Android before 1.4 and Tokyo Star bank App for iOS before 1.4 do not validate SSL certificates.
CVE-2016-1148 1 Photosynth 1 Akerun 2026-06-17 4.3 MEDIUM 8.1 HIGH
Akerun - Smart Lock Robot App for iOS before 1.2.4 does not verify SSL certificates.
CVE-2016-1132 1 Docomo 1 Shoplat 2026-06-17 5.0 MEDIUM 7.5 HIGH
Shoplat App for iOS 1.10.00 through 1.18.00 does not properly verify SSL certificates.
CVE-2016-11086 1 Oauth-ruby Project 1 Oauth-ruby 2026-06-17 5.8 MEDIUM 7.4 HIGH
lib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information.
CVE-2016-11076 1 Mattermost 1 Mattermost Server 2026-06-17 5.0 MEDIUM 5.3 MEDIUM
An issue was discovered in Mattermost Server before 3.0.0. It does not ensure that a cookie is used over SSL.
CVE-2016-10937 4 Debian, Fedoraproject, Imapfilter Project and 1 more 5 Debian Linux, Fedora, Imapfilter and 2 more 2026-06-17 5.0 MEDIUM 7.5 HIGH
IMAPFilter through 2.6.12 does not validate the hostname in an SSL certificate.
CVE-2016-10931 1 Rust-openssl Project 1 Rust-openssl 2026-06-17 6.8 MEDIUM 8.1 HIGH
An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.
CVE-2016-10536 1 Socket 1 Engine.io-client 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
engine.io-client is the client for engine.io, the implementation of a transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. The vulnerability is related to the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, certificate verification will be disabled. This is problematic as engine.io-client 1.6.8 and earlier passes in an object for settings that includes the rejectUnauthorized property, whether it has been set or not. If the value has not been explicitly changed, it will be passed in as `null`, resulting in certificate verification being turned off.
CVE-2016-10534 1 Electron-packager Project 1 Electron-packager 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
electron-packager is a command line tool that packages Electron source code into `.app` and `.exe` packages. along with Electron. The `--strict-ssl` command line option in electron-packager >= 5.2.1 <= 6.0.0 || >=6.0.0 <= 6.0.2 defaults to false if not explicitly set to true. This could allow an attacker to perform a man in the middle attack.
CVE-2016-10511 1 Twitter 1 Twitter 2026-06-17 4.3 MEDIUM 5.9 MEDIUM
The Twitter iOS client versions 6.62 and 6.62.1 fail to validate Twitter's server certificates for the /1.1/help/settings.json configuration endpoint, permitting man-in-the-middle attackers the ability to view an application-only OAuth client token and potentially enable unreleased Twitter iOS app features.
CVE-2016-1000033 2 Gnome, Redhat 2 Shotwell, Enterprise Linux 2026-06-17 4.3 MEDIUM 3.7 LOW
Shotwell version 0.22.0 (and possibly other versions) is vulnerable to a TLS/SSL certification validation flaw resulting in a potential for man in the middle attacks.
CVE-2016-1000030 2 Pidgin, Suse 2 Pidgin, Linux Enterprise Server 2026-06-17 7.5 HIGH 9.8 CRITICAL
Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutls_x509_crt_init() and gnutls_x509_crt_import() that can result in code execution. This attack appear to be exploitable via custom X.509 certificate from another client. This vulnerability appears to have been fixed in 2.11.0.