CVE-2022-38122
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 · uneditedUPSMON PRO transmits sensitive data in cleartext over HTTP protocol. An unauthenticated remote attacker can exploit this vulnerability to access sensitive data.
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 confidenceUPSMON PRO transmits sensitive data in cleartext over unencrypted HTTP, allowing any network attacker on the same broadcast domain or along the communication path to intercept and read sensitive monitoring or authentication data via packet capture.
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.57CVSS 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 if Upsmon Pro is installed and runningCheck running services or processes for Upsmon Pro, or check if the web interface is accessible on the local network by attempting to access HTTP port 80 or 443 on the device hosting the applicationAffected if Upsmon Pro version 2.57 is running and accessible on the network
-
Verify the installed versionAccess the Upsmon Pro web interface or check the application version information through its administrative interface or installed software registryAffected if The installed version is exactly 2.57 (the only affected version listed)
-
Confirm HTTP access is enabledAttempt to access the Upsmon Pro web interface via HTTP (port 80) rather than HTTPS. Check the web server configuration or try accessing http://[device_ip] to see if it respondsAffected if The web interface responds to unencrypted HTTP requests on port 80 or another non-encrypted port
-
Check if HTTPS is not enforcedObserve whether the web interface redirects HTTP to HTTPS or allows HTTP access without redirect. Inspect the browser network traffic or check configuration for TLS/HTTPS enforcement settingsAffected if HTTP requests are accepted without automatic redirect to HTTPS and sensitive data can be captured in cleartext
You are affected if Upsmon Pro version 2.57 is running and its web interface is accessible over unencrypted HTTP, allowing network attackers to intercept sensitive data via packet capture.
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 dataEnable TLS/HTTPS encryption on the UPSMON PRO web interface and disable all HTTP access to ensure all sensitive data is transmitted only over encrypted channels.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38122 — 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-38122 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