Skip to content

GHSA-p782-xgp4-8hr8 BIT-golang-2022-29526 CVE-2022-29526 GO-2022-0493

golang.org/x/sys/unix has Incorrect privilege reporting in syscall

Medium Go
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
2.95%
Chance of exploitation in the next 30 days. Higher than 87.17% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
Available
2 packages have a fixed version

Description

Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Reporting in syscall. When called with a non-zero flags parameter, the Faccessat function could incorrectly report that a file is accessible.

Specific Go Packages Affected

golang.org/x/sys/unix

Affected versions

Go

PackageVulnerableFixed in
golang.org/x/sys
< 0.0.0-20220412211240-33da011f77ad
0.0.0-20220412211240-33da011f77ad
stdlib
< 1.17.10
>= 1.18.0-0, < 1.18.2
1.17.10
1.18.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

golang.org/x/sys Go → 0.0.0-20220412211240-33da011f77ad

go
go get golang.org/x/sys@v0.0.0-20220412211240-33da011f77ad && go mod tidy

stdlib Go → 1.18.2

go
go get stdlib@v1.18.2 && go mod tidy

Severity breakdown

CVSS 3.1 5.3

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4374-p667-p6c8
HTTP/2 rapid reset can cause excessive work in net/http
High Known exploited Also affects stdlib
CVE-2020-0601
Certificate validation bypass on Windows in crypto/x509
High Known exploited Also affects stdlib
RUSTSEC-2026-0382
Distrust compromised intermediate certificates in crypto/x509
Medium Also affects stdlib
GO-2026-6613
HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http
High Also affects stdlib
GO-2026-6609
Lack of limit on size of parsed Range headers in net/http
High Also affects stdlib
GO-2026-6608
Memory limit bypass when parsing MIME headers in net/textproto, mime/multipart
High Also affects stdlib
GO-2026-6607
Reject malformed ECH outer extension references in crypto/tls
High Also affects stdlib
GO-2026-6604
Root.Mkdir(All) can follow junctions out of the root on Windows in os
Critical Also affects stdlib

Credits: Joël Gähwiler (@256dpi)

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor