CVE-2016-1000002VulnerabilityPublished 5 Nov 2019Updated 22 Jul 2026

gdm3 3.14.2 and possibly later has an information leak before screen lock

Affects gdm3Source GCVE Database

Not known to be exploited · CVSS 2.4 Low.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2019
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu:16.04:LTSgdm3`pkg:deb/ubuntu/gdm3@3.18.3-0ubuntu2.2?arch=source&distro=xenial`Other threats	Affected =3.18.0-2ubuntu1 =3.18.0-2ubuntu2 =3.18.0-2ubuntu3 =3.18.0-2ubuntu4 =3.18.2-1ubuntu1 =3.18.2-1ubuntu2 =3.18.3-0ubuntu1 =3.18.3-0ubuntu2 =3.18.3-0ubuntu2.1 =3.18.3-0ubuntu2.2	Fixed in–
Ubuntu:18.04:LTSgdm3`pkg:deb/ubuntu/gdm3@3.28.3-0ubuntu18.04.6?arch=source&distro=bionic`Other threats	Affected =3.26.1-3ubuntu2 =3.26.1-3ubuntu3 =3.26.2.1-0ubuntu1 =3.26.2.1-2ubuntu1 =3.26.2.1-2ubuntu2 =3.27.90-0ubuntu1 =3.27.92-0ubuntu1 =3.28.0-0ubuntu1 =3.28.2-0ubuntu1.2 =3.28.2-0ubuntu1.3 =3.28.2-0ubuntu1.4 =3.28.3-0ubuntu18.04.1 =3.28.3-0ubuntu18.04.3 =3.28.3-0ubuntu18.04.4 =3.28.3-0ubuntu18.04.6	Fixed in–
Ubuntu:20.04:LTSgdm3`pkg:deb/ubuntu/gdm3@3.36.3-0ubuntu0.20.04.4?arch=source&distro=focal`Other threats	Affected =3.34.1-1ubuntu1 =3.36.3-0ubuntu0.20.04.1 =3.36.3-0ubuntu0.20.04.2 =3.36.3-0ubuntu0.20.04.3 =3.36.3-0ubuntu0.20.04.4	Fixed in–
Ubuntu:22.04:LTSgdm3`pkg:deb/ubuntu/gdm3@42.0-1ubuntu7.22.04.4?arch=source&distro=jammy`Other threats	Affected =41~rc-0ubuntu2 =41.0-3ubuntu1 =41.0-3ubuntu2 =41.3-1ubuntu1 =41.3-1ubuntu2 =41.3-1ubuntu3 =42.0-1ubuntu1 =42.0-1ubuntu2 =42.0-1ubuntu4 =42.0-1ubuntu6 =42.0-1ubuntu7 =42.0-1ubuntu7.22.04.1 =42.0-1ubuntu7.22.04.2 =42.0-1ubuntu7.22.04.3 =42.0-1ubuntu7.22.04.4	Fixed in–
Ubuntu:24.04:LTSgdm3`pkg:deb/ubuntu/gdm3@46.2-1ubuntu1~24.04.9?arch=source&distro=noble`Other threats	Affected =45~beta-1ubuntu1 =45.0.1-1ubuntu1 =45.0.1-1ubuntu2 =46~rc-1ubuntu2 =46.0-2ubuntu1 =46.2-1ubuntu1~24.04.1 =46.2-1ubuntu1~24.04.3 =46.2-1ubuntu1~24.04.4 =46.2-1ubuntu1~24.04.5 =46.2-1ubuntu1~24.04.6 =46.2-1ubuntu1~24.04.7 =46.2-1ubuntu1~24.04.9	Fixed in–
Ubuntu:25.10gdm3`pkg:deb/ubuntu/gdm3@49.0.1-1ubuntu2.2?arch=source&distro=questing`Other threats	Affected =48.0-1ubuntu1 =49~alpha.0-0ubuntu1 =49~alpha.1-0ubuntu1 =49~alpha.1-0ubuntu2 =49~beta-0ubuntu1 =49~beta-0ubuntu2 =49~beta-0ubuntu3 =49~rc-0ubuntu1 =49~rc-0ubuntu2 =49.0.1-1ubuntu1 =49.0.1-1ubuntu2 =49.0.1-1ubuntu2.1 =49.0.1-1ubuntu2.2	Fixed in–
Ubuntu:26.04:LTSgdm3`pkg:deb/ubuntu/gdm3@50.1-0ubuntu0.1?arch=source&distro=resolute`Other threats	Affected =49.0.1-1ubuntu2 =49.2-1ubuntu3 =49.2-1ubuntu4 =50~beta-0ubuntu3 =50~rc-0ubuntu1 =50.0-0ubuntu1 =50.1-0ubuntu0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, physical security controls to prevent unauthorized access before screen lock activation are recommended.

Description

gdm3 version 3.14.2 and possibly later versions contain an information leak vulnerability that occurs before the screen lock activates. This vulnerability may expose sensitive information prior to the screen being locked, potentially allowing unauthorized access to certain data. The issue affects multiple specific Ubuntu package versions of gdm3 across several Ubuntu LTS releases and other versions. No known exploits in the wild have been reported. The vulnerability has a CVSS 3.1 vector indicating low impact on confidentiality with no impact on integrity or availability.

References

Community reviews

Loading reviews…