CVE-2022-45177
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 · uneditedAn issue was discovered in LIVEBOX Collaboration vDesk through v031. An Observable Response Discrepancy can occur under the /api/v1/vdeskintegration/user/isenableuser endpoint, the /api/v1/sharedsearch?search={NAME]+{SURNAME] endpoint, and the /login endpoint. The web application provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
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 confidenceLIVEBOX Collaboration vDesk through v031 contains an Observable Response Discrepancy vulnerability where the application returns different HTTP responses (timing, status codes, or content) for the same request depending on internal state, allowing unauthorized enumeration or information gathering via the /api/v1/vdeskintegration/user/isenableuser, /api/v1/sharedsearch, and /login endpoints.
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<= 031CVSS 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 the installed vDesk versionAccess the Liveboxcloud Vdesk administration interface, typically via the About or Settings page, or query the /api/v1/version endpoint if available. Compare the version number to the affected range (<= 031).Affected if The installed version is v031 or earlier.
-
Confirm the /api/v1/vdeskintegration/user/isenableuser endpoint is accessibleSend a GET or POST request to https://[host]/api/v1/vdeskintegration/user/isenableuser with varying user identifiers (valid and invalid). Observe whether the HTTP response status codes, timing, or body content differ between requests.Affected if The endpoint responds differently based on whether the user identifier is valid or invalid.
-
Confirm the /api/v1/sharedsearch endpoint is accessibleSend search requests to https://[host]/api/v1/sharedsearch with different query parameters (valid search terms vs. malformed or non-existent terms). Compare the HTTP responses received.Affected if The endpoint returns distinguishable differences in status codes, response bodies, or timing between valid and invalid search queries.
-
Confirm the /login endpoint is accessible and exhibits response discrepanciesSend authentication attempts to https://[host]/login using both valid credentials and invalid/fictional credentials. Compare the HTTP responses including status codes, error messages, and response times.Affected if The login endpoint reveals different responses for valid versus invalid usernames or passwords (e.g., different error messages, timing differences indicating username validity).
Your environment is affected if Liveboxcloud Vdesk version is v031 or earlier AND any of the three affected endpoints (/api/v1/vdeskintegration/user/isenableuser, /api/v1/sharedsearch, /login) are accessible and return inconsistent responses based on input validity.
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 uniform response handling across all endpoints so that valid and invalid requests return consistent responses regardless of internal state; add authentication/authorization checks to protected endpoints and consider rate limiting to further reduce information leakage.
- Consultation4.0 h
- Implementation10.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45177 — 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-45177 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