CVE-2022-45177 is a high severity (CVSS 7.5) observable response discrepancy in LIVEBOX Collaboration vDesk, versions through v031. Three endpoints answer differently in ways that reveal internal state. No fixed version could be confirmed, so contact LIVEBOX and limit exposure of the product.
What's affected
The record says LIVEBOX Collaboration vDesk through v031 is affected. Three places answer requests differently in a way that reveals internal state to an unauthorized actor: a user status endpoint, a shared search endpoint and the login page. The record cites a Gruppo TIM vulnerability research page. The page I fetched is a general page about TIM's coordinated disclosure program and did not describe this issue, so I could not confirm fixed versions or a vendor advisory.
The record scores it 7.5 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. It lists two weakness classes, CWE-203 (Observable Discrepancy) and CWE-94 (Improper Control of Generation of Code).
A note on the second class. The description talks about differing responses that reveal information, which matches the first class. Code injection does not obviously match that description, so the second label may be an error in the record. I mention both because the record does.
How to check if you're exposed
You cannot confirm exposure from a version alone, because no fixed version is named. Find which vDesk version you run and compare it with v031.
Defenders can test their own login and lookup behavior. Compare the response body, status code and timing for a real account name and a made up one against your own instance, with permission, and see whether they differ. A difference means an attacker can learn which accounts exist. Do this only on systems you are authorized to test.
What to do now
- Confirm whether you run LIVEBOX Collaboration vDesk and which version.
- Ask LIVEBOX for the fixed version and any interim advice.
- Put rate limiting and monitoring in front of the login and lookup endpoints.
- Enable multi-factor authentication where the product supports it, so that a discovered account name is not enough.
- Watch authentication logs for bursts of failed or unusual lookups.
Why it matters
An observable response discrepancy means the application answers differently depending on a hidden fact. A login form that says one thing for a real user name and another for an unknown one lets an outsider test lists of names and learn which accounts exist. That information feeds password guessing and phishing.
The record rates the impact as high on confidentiality only, with no privileges required, which is why it reaches 7.5. The weakness does not change data by itself. Its harm is the head start it gives to a second attack. The usual fix is to return the same response whatever the cause of failure. The record's KEV flag is false and I found no report of exploitation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why does the record list code injection as well?
The description does not describe code injection, so the label may be a mistake in the record. I flag both.
Is there a patch?
I could not confirm one. Ask LIVEBOX.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.