Vulnerabilities (CVE)

Filtered by CWE-311
Total 527 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2014-2379 1 Sensysnetworks 4 Trafficdot, Vds, Vsn240-f and 1 more 2026-06-17 4.3 MEDIUM N/A
Sensys Networks VSN240-F and VSN240-T sensors VDS before 2.10.1 and TrafficDOT before 2.10.3 do not use encryption, which allows remote attackers to interfere with traffic control by replaying transmissions on a wireless network.
CVE-2012-5474 4 Debian, Fedoraproject, Openstack and 1 more 4 Debian Linux, Fedora, Horizon and 1 more 2026-06-16 2.1 LOW 5.5 MEDIUM
The file /etc/openstack-dashboard/local_settings within Red Hat OpenStack Platform 2.0 and RHOS Essex Release (python-django-horizon package before 2012.1.1) is world readable and exposes the secret key value.
CVE-2012-1977 1 Wellintech 1 Kingview 2026-06-16 7.1 HIGH N/A
WellinTech KingSCADA 3.0 uses a cleartext base64 format for storage of passwords in user.db, which allows context-dependent attackers to obtain sensitive information by reading this file.
CVE-2011-3355 2 Gnome, Linux 2 Evolution-data-server3, Linux Kernel 2026-06-16 4.3 MEDIUM 7.3 HIGH
evolution-data-server3 3.0.3 through 3.2.1 used insecure (non-SSL) connection when attempting to store sent email messages into the Sent folder, when the Sent folder was located on the remote server. An attacker could use this flaw to obtain login credentials of the victim.
CVE-2010-3299 2 Debian, Rubyonrails 2 Debian Linux, Rails 2026-06-16 4.3 MEDIUM 6.5 MEDIUM
The encrypt/decrypt functions in Ruby on Rails 2.3 are vulnerable to padding oracle attacks.
CVE-2010-3292 1 Mailscanner 1 Mailscanner 2026-06-16 2.1 LOW 5.5 MEDIUM
The update{_bad,}_phishing_sites scripts in mailscanner 4.79.11-2 downloads files and trusts them without using encryption (e.g., https) or digital signature checking which could allow an attacker to replace certain configuration files (e.g., phishing whitelist) via dns/packet spoofing.
CVE-2007-4961 1 Lindenlab 1 Second Life 2026-06-16 4.3 MEDIUM 7.5 HIGH
The login_to_simulator method in Linden Lab Second Life, as used by the secondlife:// protocol handler and possibly other Second Life login mechanisms, sends an MD5 hash in cleartext in the passwd field, which allows remote attackers to login to an account by sniffing the network and then sending this hash to a Second Life authentication server.