CVE-2022-35582
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 · uneditedPenta Security Systems Inc WAPPLES 4.0.*, 5.0.0.*, 5.0.12.* are vulnerable to Incorrect Access Control. The operating system that WAPPLES runs on has a built-in non-privileged user penta with a predefined password. The password for this user, as well as its existence, is not disclosed in the documentation. Knowing the credentials, attackers can use this feature to gain uncontrolled access to the device and therefore are considered an undocumented possibility for remote control.
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 · high confidencePenta Security WAPPLES versions 4.0.*, 5.0.0.*, and 5.0.12.* contain an undocumented built-in non-privileged user account named 'penta' with a predefined password that is not disclosed in product documentation. Attackers who discover these credentials can bypass authentication controls and gain unauthorized access to the device.
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= 4.0.0= 5.0.0.0= 5.0.12.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 WAPPLES installation and versionLocate the WAPPLES installation directory or check system inventory for 'Penta Security WAPPLES' and retrieve the installed version number (e.g., via product console, About page, or version file in installation directory)Affected if Installed version is 4.0.x, 5.0.0.x, or 5.0.12.0 (matching the ranges 4.0.*, 5.0.0.*, 5.0.12.*)
-
Check for the undocumented penta user accountAccess the WAPPLES administrative interface or user configuration files and list all user accounts; look for an account named 'penta' that is not documented in official product documentationAffected if A user account named 'penta' exists in the system and is not documented in the product manual
-
Verify penta account is active and usableCheck the user account status in WAPPLES user management (via admin console or configuration database); determine if the account is enabled and capable of authenticatingAffected if The 'penta' account exists and is enabled for authentication
-
Review authentication logs for penta account usageExamine WAPPLES authentication and access logs for any login attempts, successful authentications, or actions performed using the 'penta' user accountAffected if There are any authentication events or actions associated with the 'penta' user account, especially from unexpected sources or IP addresses
A user is affected if they are running a WAPPLES version in the 4.0.x, 5.0.0.x, or 5.0.12.x range AND the undocumented 'penta' user account exists and is enabled on their system.
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 dataChange or disable the undocumented 'penta' user account on affected WAPPLES devices immediately; contact Penta Security for guidance on secure configuration and verify no other undocumented accounts exist.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35582 — 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-35582 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