CVE-2023-28339
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenDoas through 6.8.2, when TIOCSTI is available, allows privilege escalation because of sharing a terminal with the original session. NOTE: TIOCSTI is unavailable in OpenBSD 6.0 and later, and can be made unavailable in the Linux kernel 6.2 and later.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenDoas through 6.8.2 contains a privilege escalation vulnerability via the TIOCSTI ioctl. When OpenDoas maintains a connection to the user's terminal and TIOCSTI is available, a local attacker can inject commands into the terminal's input buffer that will be executed with the elevated privileges of the running process, allowing local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.8.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OpenDoas versionRun 'doas --version' or check via package manager (dpkg -l | grep -i opendoas, rpm -q opendoas, or apk list opendoas)Affected if Version is 6.8.2 or lower
-
Verify TIOCSTI ioctl availabilityCheck kernel version with 'uname -r' - on kernels 6.2+ check if TIOCSTI has been disabled via kernel config or sysctl. For older kernels, TIOCSTI is typically available by defaultAffected if Running kernel is older than 6.2 and TIOCSTI remains enabled, or kernel 6.2+ with TIOCSTI not disabled via CONFIG_LEGACY_TIOCSTI=n or sysctl
-
Confirm OpenDoas is in useCheck if the doas binary exists and is accessible (ls -la /usr/bin/doas or /usr/sbin/doas) and verify doas.conf exists (ls /etc/doas.conf)Affected if OpenDoas is installed and configured on the system with terminal-connected execution context
User is affected if OpenDoas version 6.8.2 or lower is installed on a system where TIOCSTI ioctl is available and OpenDoas maintains a terminal connection during execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable TIOCSTI in the Linux kernel (6.2+) via kernel configuration or upgrade OpenDoas beyond version 6.8.2 if a patched version is available. On systems where TIOCSTI cannot be disabled, restrict terminal access and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28339 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data