CVE-2022-47561
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 web application stores credentials in clear text in the "admin.xml" file, which can be accessed without logging into the website, which could allow an attacker to obtain credentials related to all users, including admin users, in clear text, and use them to subsequently execute malicious 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 · high confidenceThe web application stores user credentials in clear text within an 'admin.xml' file. This file is accessible without authentication, allowing any unauthenticated attacker to download the file and obtain plaintext passwords for all users including administrators.
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= 601j= 601jCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 firmware versionAccess the device's web interface or check system information to determine the installed firmware version. Look for version information in the device dashboard, about page, or system settings.Affected if The firmware version is exactly 601j for either Ekorccp or Ekorrci product lines
-
Locate the admin.xml fileAttempt to access the file via HTTP/HTTPS using common paths such as: http://[device-ip]/admin.xml, http://[device-ip]/config/admin.xml, or http://[device-ip]/web/admin.xml. Check the web root directory for any XML configuration files.Affected if The admin.xml file exists and is accessible via web request without authentication
-
Inspect admin.xml for plaintext credentialsDownload or view the contents of the admin.xml file. Search within the file for password fields, credential entries, or user account data stored in clear text.Affected if The file contains plaintext passwords or other credential data in plain text format (not hashed or encrypted)
-
Verify unauthenticated accessAttempt to access the admin.xml file from an incognito browser window or using curl/wget without providing any login credentials or session cookies.Affected if The file can be downloaded or viewed without any authentication required
You are affected if your device runs firmware version 601j AND the admin.xml file is accessible without authentication and contains plaintext passwords.
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 dataImplement secure credential storage using strong hashing (e.g., bcrypt, Argon2) instead of plaintext storage, and configure proper access controls to prevent unauthorized access to sensitive configuration files like admin.xml.
- Consultation4.0 h
- Implementation16.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 $8,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47561 — 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-47561 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