CVE-2016-7798: Weak Encryption
First published: Mon Jan 30 2017(Updated: )
Last updated 24 July 2024
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/ruby-attr-encrypted | 3.1.0-3 3.1.0-4 4.1.0-1 | |
| debian/ruby-encryptor | 3.0.0-2 | |
| Ruby-lang OpenSSL | <2.0.0 | |
| Debian Linux | =8.0 | |
| Debian Linux | =9.0 | |
| <2.0.0 | ||
| =8.0 | ||
| =9.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.openwall.com/lists/oss-security/2016/09/19/9
- http://www.openwall.com/lists/oss-security/2016/09/30/6
- http://www.openwall.com/lists/oss-security/2016/10/01/2
- http://www.securityfocus.com/bid/93031
- https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062
- https://github.com/ruby/openssl/issues/49
- https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html
- https://www.debian.org/security/2017/dsa-3966
- https://launchpad.net/bugs/cve/CVE-2016-7798
- https://github.com/attr-encrypted/attr_encrypted/issues/203
- https://github.com/attr-encrypted/encryptor/pull/22
- https://security-tracker.debian.org/tracker/CVE-2016-7798
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7798
- https://nvd.nist.gov/vuln/detail/CVE-2016-7798
- https://ubuntu.com/security/CVE-2016-7798
Frequently Asked Questions
What is the severity of CVE-2016-7798?
CVE-2016-7798 is categorized with a high severity due to its impact on encryption integrity.
How do I fix CVE-2016-7798?
To fix CVE-2016-7798, update the Ruby openssl gem to versions that address the vulnerability.
Which software is affected by CVE-2016-7798?
CVE-2016-7798 affects the openssl gem in Ruby and specifically certain versions of ruby-attr-encrypted and ruby-encryptor packages.
What could potentially happen if CVE-2016-7798 is exploited?
If exploited, CVE-2016-7798 could allow attackers to bypass the encryption protection mechanism, compromising sensitive data.
Is CVE-2016-7798 still a concern today?
Yes, CVE-2016-7798 remains a concern, especially in legacy systems using vulnerable versions of the software.
- agent/type
- agent/remedy
- collector/launchpad-cve
- source/Launchpad
- agent/weakness
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/first-publish-date
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/author
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- package-manager/debian
- vendor/ruby-lang
- canonical/ruby-lang openssl
- vendor/debian
- canonical/debian linux
- version/debian linux/8.0
- version/debian linux/9.0