CVE-2022-47892
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 · uneditedAll versions of NetMan 204 could allow an unauthenticated remote attacker to read a file (config.cgi) containing sensitive information, like credentials.
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 confidenceNetMan 204 contains an unauthenticated file disclosure vulnerability allowing remote attackers to read the config.cgi file, which contains sensitive credentials. This is likely a path traversal or insecure file inclusion issue in the web interface.
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 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 NetMan 204 installationCheck if the Riello UPS NetMan 204 web interface is accessible on your network by accessing the device IP or hostname on the typical HTTP/HTTPS ports (80/443). Look for the NetMan 204 login page or banner.Affected if The NetMan 204 web interface is present and reachable on your network.
-
Verify config.cgi file existenceAttempt to access the config.cgi file directly via HTTP/HTTPS without any authentication. For example: GET http://<device_ip>/cgi-bin/config.cgi or the full path as discovered in your environment.Affected if The config.cgi file is accessible without requiring login credentials.
-
Check for sensitive content in config.cgiIf config.cgi is accessible, examine the response content for plaintext credentials, SNMP community strings, user accounts, or other sensitive configuration data.Affected if config.cgi returns sensitive information such as usernames, passwords, community strings, or authentication tokens.
-
Assess network exposureDetermine whether the NetMan 204 web interface is accessible from untrusted networks (e.g., the internet or guest networks) versus being restricted to trusted management networks.Affected if The web interface is reachable from networks that should not have direct management access to the UPS device.
If the NetMan 204 web interface is present and the config.cgi file can be accessed without authentication to reveal sensitive credentials, the environment is affected by CVE-2022-47892.
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 dataRestrict external access to the NetMan 204 web interface via network segmentation or firewall rules. If possible, relocate or restrict access to the config.cgi file and implement authentication. Contact vendor for patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47892 — 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-47892 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