LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31072: Octokit gem published with world-writable files

Octokit is a Ruby toolkit for the GitHub API. Versions 4.23.0 and 4.24.0 of the octokit gem were published containing world-writeable files. Specifically, the gem was packed with files having their permissions set to `-rw-rw-rw-` (i.e. 0666) instead of `rw-r--r--` (i.e. 0644). This means everyone who is not the owner (Group and Public) with access to the instance where this release had been installed could modify the world-writable files from this gem. This issue is patched in Octokit 4.25.0. Two workarounds are available. Users can use the previous version of the gem, v4.22.0. Alternatively, users can modify the file permissions manually until they are able to upgrade to the latest version.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Octokit Ruby gem versions 4.23.0 and 4.24.0 were shipped with files writable by any local user on the installed system. An attacker would need local access, but could alter gem files and affect application integrity. Octokit 4.25.0 fixes the packaging permissions issue.

Executive priority

Treat this as a low-severity hygiene issue with integrity implications. It does not indicate remote compromise, but affected shared systems should be corrected promptly because local users could modify application dependency files.

Technical view

The issue is CWE-276: incorrect default permissions. The affected gem releases contain files with mode 0666 instead of 0644, allowing group and public write access on systems where those files are installed. CVSS is 2.5 low, with local attack vector, high complexity, and low integrity impact.

Likely exposure

Exposure is limited to Ruby applications or environments that installed octokit gem 4.23.0 or 4.24.0. Risk is higher on shared servers, CI runners, developer machines, or containers where another local user can reach the installed gem path.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not marked KEV. Abuse requires local low-privileged access and the ability to modify the installed world-writable gem files. The main concern is unauthorized code or file tampering, not remote compromise.

Researcher notes

The advisory clearly defines the affected range, root cause, patch version, and workarounds. No source in the bundle provides exploit evidence beyond the permission weakness itself. Validation should focus on installed gem versions and file modes, especially in reused build artifacts.

Mitigation direction

  • Upgrade octokit to version 4.25.0 or later.
  • If upgrade is blocked, use octokit version 4.22.0.
  • Manually change affected gem file permissions from 0666 to 0644.
  • Rebuild affected deployment images after updating the gem.
  • Prioritize remediation on shared hosts and CI systems.

Validation and detection

  • Check dependency manifests and lockfiles for octokit 4.23.0 or 4.24.0.
  • Inspect installed octokit gem files for world-writable permissions.
  • Confirm production images no longer contain the vulnerable gem versions.
  • Verify CI and developer environments use a fixed or unaffected version.
  • Review local multi-user access where affected gems were installed.
Prepared
Confidence
high
Sources
4

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.

cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31072 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
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

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

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
3Source 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
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2022-31072Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
octokitoctokit.rb>= 4.23.0, < 4.25.0Listed
Weakness

CWE details

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.