LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27803: A vulnerability was discovered in how p2p/p2p_pd.c in wpa_supplicant before 2.10 processes P2P (Wi-Fi Direc...

A vulnerability was discovered in how p2p/p2p_pd.c in wpa_supplicant before 2.10 processes P2P (Wi-Fi Direct) provision discovery requests. It could result in denial of service or other impact (potentially execution of arbitrary code), for an attacker within radio range.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-27803 affects wpa_supplicant before 2.10 when handling Wi-Fi Direct provision discovery requests. An attacker must be within radio range, but no account or user interaction is required. The cited impact includes denial of service and potentially arbitrary code execution.

Executive priority

Treat as a high-priority wireless-adjacent risk for affected fleets, especially laptops and devices in public or shared spaces. It is less urgent than internet-exposed remote code execution, but patching should not wait where wpa_supplicant is outdated.

Technical view

The flaw is in p2p/p2p_pd.c P2P provision discovery request processing in wpa_supplicant before 2.10. CVSS 3.1 is 7.5 with adjacent-network attack vector, high complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant on systems running wpa_supplicant before 2.10 with Wi-Fi Direct/P2P capability. The attacker must be physically nearby or otherwise within radio range, so this is not a typical internet-facing exposure.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public sources describe the vulnerability and fixes, but exploitation requires adjacent radio access and appears high complexity per CVSS.

Researcher notes

Evidence supports wpa_supplicant before 2.10, P2P provision discovery handling, and adjacent radio-range attack requirements. The bundle does not provide proof of active exploitation. Downstream Debian and Fedora advisories indicate vendor patch availability.

Mitigation direction

  • Upgrade wpa_supplicant to 2.10 or a vendor-patched package.
  • Apply Debian, Fedora, or other distribution security updates where applicable.
  • Use the upstream patch if maintaining a custom wpa_supplicant build.
  • Check vendor guidance for supported interim risk-reduction options.
  • Prioritize mobile, workstation, and wireless-enabled systems using P2P features.

Validation and detection

  • Inventory installed wpa_supplicant versions across wireless-capable endpoints.
  • Confirm vendor package versions include the CVE-2021-27803 fix.
  • Identify systems where Wi-Fi Direct/P2P is enabled or required.
  • Verify vulnerability scanner findings against package changelogs and vendor advisories.
  • Track exceptions for devices awaiting vendor firmware or package updates.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-27803 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-27803Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.