CVE-2020-25708: A divide by zero issue was found to occur in libvncserver-0.9.12.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libvncserver (AlmaLinux:8) 0.9.11-17.el8; libvncserver-devel (AlmaLinux:8) 0.9.11-17.el8; libvncserver (Debian:10) 0.9.11+dfsg-1.3+deb10u5.
Low priority for now. Upgrade to libvncserver (AlmaLinux:8) 0.9.11-17.el8; libvncserver-devel (AlmaLinux:8) 0.9.11-17.el8; libvncserver (Debian:10) 0.9.11+dfsg-1.3+deb10u5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A divide by zero issue was found to occur in libvncserver-0.9.12. A malicious client could use this flaw to send a specially crafted message that, when processed by the VNC server, would lead to a floating point exception, resulting in a denial of service.
- Published
- Nov 27, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 76th percentile
- CWE
- CWE-369
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libvncserver project | libvncserver | cpe:2.3:a:libvncserver_project:libvncserver |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- libvncserver project libvncserver0.9.12
- redhat enterprise linux6.0
- redhat enterprise linux7.0
- redhat enterprise linux8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a libvncserver
- libvncserver 0.9.12affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libvncserver | before 0.9.11-17.el8 | 0.9.11-17.el8 |
| AlmaLinux:8 | libvncserver-devel | before 0.9.11-17.el8 | 0.9.11-17.el8 |
| Debian:10 | libvncserver | before 0.9.11+dfsg-1.3+deb10u5 | 0.9.11+dfsg-1.3+deb10u5 |
| Debian:12 | libvncserver | before 0.9.13+dfsg-1 | 0.9.13+dfsg-1 |
| Debian:9 | libvncserver | before 0.9.11+dfsg-1.3~deb9u6 | 0.9.11+dfsg-1.3~deb9u6 |
| openSUSE:Leap 15.1 | LibVNCServer | before 0.9.10-lp151.7.12.1 | 0.9.10-lp151.7.12.1 |
| openSUSE:Leap 15.2 | LibVNCServer | before 0.9.10-lp152.9.8.1 | 0.9.10-lp152.9.8.1 |
| Red Hat:enterprise_linux:8::appstream | libvncserver | before 0:0.9.11-17.el8 | 0:0.9.11-17.el8 |
| Red Hat:enterprise_linux:8::appstream | libvncserver-debuginfo | before 0:0.9.11-17.el8 | 0:0.9.11-17.el8 |
| Red Hat:enterprise_linux:8::appstream | libvncserver-debugsource | before 0:0.9.11-17.el8 | 0:0.9.11-17.el8 |
| Red Hat:enterprise_linux:8::crb | libvncserver-devel | before 0:0.9.11-17.el8 | 0:0.9.11-17.el8 |
| Rocky Linux:8 | libvncserver | before 0:0.9.11-17.el8 | 0:0.9.11-17.el8 |
| SUSE:HPE Helion OpenStack 8 | LibVNCServer | before 0.9.9-17.34.1 | 0.9.9-17.34.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP1 | LibVNCServer | before 0.9.10-4.25.1 | 0.9.10-4.25.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | LibVNCServer | before 0.9.1-160.22.1 | 0.9.1-160.22.1 |
Same product
libvncserver project: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7225An issue was discovered in LibVNCServer through 0.9.11.41Plan
- CVE-2017-18922It was discovered that websockets.c in LibVNCServer prior to 0.9.12 did not properly decode certain WebSocket frames.40Plan
- CVE-2016-9942Heap-based buffer overflow in ultra.c in LibVNCClient in LibVNCServer before 0.9.11 allows remote servers to cause a denial of service (appl40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-14400Jun 17, 2020 · An issue was discovered in LibVNCServer before 0.9.13.31Monitor
- ← EarlierCVE-2020-14401Jun 17, 2020 · An issue was discovered in LibVNCServer before 0.9.13.27Monitor
- Later →CVE-2020-29260Sep 2, 2022 · libvncclient v0.9.13 was discovered to contain a memory leak via the function rfbClientCleanup().30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:libvncserver | 0.9.11-17.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libvncserver-devel | 0.9.11-17.el8 · AlmaLinux:8 | Package registry (OSV) |
| debian:libvncserver | 0.9.13+dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:LibVNCServer | 0.9.10-lp152.9.8.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:libvncserver | 0:0.9.11-17.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libvncserver-debuginfo | 0:0.9.11-17.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libvncserver-debugsource | 0:0.9.11-17.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libvncserver-devel | 0:0.9.11-17.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| rocky linux:libvncserver | 0:0.9.11-17.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:LibVNCServer | 0.9.1-160.22.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.