Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-2097 medium CVSS 5.3

Vulnerability in Siemens Openssl (CVE-2022-2097)

Summary

Vulnerability in Siemens Openssl (CVE-2022-2097). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was pre-existing in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed.

Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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 CVE-2022-2097 has been found in Siemens Openssl.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Siemens Openssl CVE-2022-2097" on the vendor's site.

CVE-2022-2097 (Siemens Openssl) — CWE-327 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Affected: 3.0.0 - 3.0.4
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.

❓ What is the problem

A vulnerability (CWE-327) exists in Siemens Openssl.

📍 Affected scope

Affected versions of Siemens Openssl: 3.0.0 - 3.0.4.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory. (If a vulnerable version 3.0.0 - 3.0.4 is in production, plan an immediate maintenance window.)

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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. 1
    Identify exposure identify 
    grep -r 'Openssl' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Openssl を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Match against affected range verify 
    Confirm if version satisfies `3.0.0 - 3.0.4`

    Step 1 で見つかったバージョンが影響範囲 3.0.0 - 3.0.4 に該当するか照合。本番で稼働中ならインシデント扱い。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

crates.io openssl-src
[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.9"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details