Skip to main content
Public proof of conceptFix available

CVE-2023-28102

A public proof of concept exists; no exploitation attested.

  • Published2023-03-27
  • Fixed in3.4.3
  • WeaknessCWE-78

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

discordrb is an implementation of the Discord API using Ruby. In discordrb before commit `91e13043ffa` the `encoder.rb` file unsafely constructs a shell string using the file parameter, which can potentially leave clients of discordrb vulnerable to command injection. The library is not directly exploitable: the exploit requires that some client of the library calls the vulnerable method with user input. However, if unsafe input reaches the library method, then an attacker can execute arbitrary shell commands on the host machine. Full impact will depend on the permissions of the process running the `discordrb` library and will likely not be total system access. This issue has been addressed in code, but a new release of the `discordrb` gem has not been uploaded to rubygems. This issue is also tracked as `GHSL-2022-094`.

Timeline

dates in UTC
  1. 2023-03-2722:15CVE publishedNVD

Versions per branch

OSV · NVD
discordrb
BranchAffectedFixed in
3.4< 3.4.33.4.3
Discordrb project discordrb
BranchAffectedFixed in
2023.x< 2023-03-082023-03-08

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • shardlab discordrb
    Affected
    • = <= 3.4.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-03-27

Fix

  1. Update discordrb to 3.4.3

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2025-02-19
  • CNACVSS 3.18.3known since 2026-10-23
  • NVDCVSS 3.19.6read 2026-10-23
  • CNAweakness (CWE)CWE-78known since 2026-10-23
  • FIRST EPSSEPSS score2.6 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2024-03-14

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Published
2023-03-27
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-8832-4mm5-x2r6

Frequently asked questions

What is CVE-2023-28102?

discordrb is an implementation of the Discord API using Ruby. In discordrb before commit `91e13043ffa` the `encoder.rb` file unsafely constructs a shell string using the file parameter, which can potentially leave clients of discordrb vulnerable to command injection. The library is not directly exploitable: the exploit requires that some client of the library calls the vulnerable method with user input. However, if unsafe input reaches the library method, then an attacker can execute arbitrary shell commands on the host machine. Full impact will depend on the permissions of the process running the `discordrb` library and will likely not be total system access. This issue has been addressed in code, but a new release of the `discordrb` gem has not been uploaded to rubygems. This issue is also tracked as `GHSL-2022-094`.

Is CVE-2023-28102 actively exploited?

A proof-of-concept exploit exists for CVE-2023-28102, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-28102?

CVE-2023-28102 has a CVSS v3 base score of 9.6 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.

Running discordrb? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record