CVE-2022-46140
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAffected devices use a weak encryption scheme to encrypt the debug zip file. This could allow an authenticated attacker to decrypt the contents of the file and retrieve debug information about the system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAffected devices implement a weak encryption scheme for debug zip files. An attacker with valid authentication credentials can exploit this vulnerability to decrypt the debug archive and access sensitive system information that was intended to be protected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device management interface or use SNMP/sysinfo commands to confirm the exact model number and firmware version. Compare against the list of affected products: Ruggedcom Rm1224 (LTE 4G EU/NAM), Scalance M804pb, M812, M816, M826, M874-2, M874-3.Affected if The device model matches any of the affected products listed in the CVE.
-
Check if debug feature is enabledNavigate to the device diagnostic or maintenance settings in the web management interface or CLI. Look for options related to debug logging, diagnostics export, or technical support bundle generation.Affected if Debug or diagnostics export functionality is enabled on the device.
-
Locate debug archive filesInspect the device filesystem or any exported backup/diagnostic files for compressed archives (zip files) that contain system diagnostics, logs, or support bundles.Affected if Debug zip archives exist on the device or have been exported.
-
Inspect encryption configurationExamine the device configuration files or settings related to archive encryption. Look for parameters specifying the encryption algorithm, key derivation method, and IV generation for debug exports.Affected if The encryption scheme uses a weak algorithm or lacks proper key derivation and random IV generation.
-
Check for hardcoded keysReview configuration files or firmware binaries for hardcoded encryption keys, default passwords, or static secrets used for encrypting debug archives.Affected if Hardcoded or static encryption keys are found in the device configuration or firmware.
The device is affected if it is one of the listed Siemens Ruggedcom or Scalance models with debug export functionality enabled and uses the default weak encryption scheme for diagnostic archives.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the weak encryption scheme with a strong, industry-standard algorithm (e.g., AES-256-GCM) with proper key derivation and random IV generation. Ensure debug files are encrypted with keys derived from secure random sources and not hardcoded.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-46140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data