CVE-2022-22987
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 · uneditedThe affected product has a hardcoded private key available inside the project folder, which may allow an attacker to achieve Web Server login and perform further actions.
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 confidenceA hardcoded private key is embedded in the project folder of the affected product, enabling attackers to bypass authentication and gain Web Server login access. This critical credential exposure allows complete compromise of the web server.
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 data<= 2.6.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 firmware versionAccess the Advantech Adam 3600 device management interface or use the device's command-line interface to retrieve the current firmware version. Check the device info or system status page for the firmware build number.Affected if The firmware version is 2.6.2 or lower.
-
Locate project folder contentsIf you have access to the device's file system (via FTP, SSH, or by extracting the firmware image), navigate to the project folder and list all files. Look for any file with extensions such as .key, .pem, .priv, or similar that may contain cryptographic material.Affected if A private key file exists in the project folder that was not intentionally placed there by the administrator.
-
Inspect private key fileOpen any suspicious key files found in the project folder using a text editor. Examine the file for PEM-style headers (-----BEGIN RSA PRIVATE KEY----- or similar) and verify if the key appears to be hardcoded rather than dynamically generated.Affected if The file contains a private key with standard PEM formatting that is embedded in the firmware.
-
Check web server authentication mechanismReview the web server configuration files in the firmware to determine if the web login functionality relies on or references the private key found in the project folder.Affected if The web server authentication is configured to use the hardcoded private key for login validation.
The device is affected if the Advantech Adam 3600 firmware version is 2.6.2 or lower and a hardcoded private key file is present in the project folder, allowing potential authentication bypass to the web server.
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 hardcoded private key with a securely generated key, implement proper secret management (e.g., environment variables, secrets vault), rotate all potentially exposed credentials, and audit for any other hardcoded secrets in the codebase.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22987 — 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-22987 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