Vulnerability in openssl
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-1543 has been found in openssl.
Confidential information can be exposed externally.
What to do: upgrade openssl to 1.1.1c-1 or later.
If unsure, ask your IT team or search "openssl DEBIAN-CVE-2019-1543" on the vendor's site.
DEBIAN-CVE-2019-1543 (openssl)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Affected: 1.1.1 - 1.1.1b
Patched: 1.1.1c-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in openssl.
Affected versions of openssl: 1.1.1 - 1.1.1b.
Severity: ?. Confidential information can be exposed externally.
Update to 1.1.1c-1. (If a vulnerable version 1.1.1 - 1.1.1b is in production, plan an immediate maintenance window.)
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openssl' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'openssl' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
opensslを grep し、稼働しているサービス・バージョンを把握する。 -
2
Match against affected rangeverify
Confirm if version satisfies `1.1.1 - 1.1.1b`Step 1 で見つかったバージョンが影響範囲
1.1.1 - 1.1.1bに該当するか照合。本番で稼働中ならインシデント扱い。 -
3
Apply patchpatch
Upgrade openssl to 1.1.1c-1ステージング環境で 1.1.1c-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | openssl |
< 1.1.1c-1 |
1.1.1c-1 |
| Debian:13 | openssl |
< 1.1.1c-1 |
1.1.1c-1 |
| Debian:14 | openssl |
< 1.1.1c-1 |
1.1.1c-1 |
Original description The description as published by the source.
ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this…
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org