LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53161: The buffered-reader crate before 1.1.5 for Rust allows out-of-bounds array access and a panic.

The buffered-reader crate before 1.1.5 for Rust allows out-of-bounds array access and a panic.

LowCVSS 2.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity flaw in the Rust buffered-reader crate. A vulnerable version can panic from out-of-bounds array access, causing limited availability impact. The provided sources do not show data theft, privilege escalation, remote compromise, or active exploitation.

Executive priority

Treat as routine dependency maintenance, not an emergency response. Schedule upgrade through normal patch cycles, with faster handling for file-processing workflows where crashes could affect operations.

Technical view

CVE-2023-53161 maps to CWE-125 and affects buffered-reader before 1.1.5. CVSS 3.1 is 2.9 with local attack vector, high complexity, no confidentiality or integrity impact, and low availability impact. The failure mode is an out-of-bounds access leading to panic.

Likely exposure

Exposure is likely limited to Rust applications that depend on sequoia-pgp buffered-reader versions before 1.1.5 and exercise affected reader code paths. Prioritize products processing untrusted local files or inputs through this crate.

Exploitation context

The bundle lists KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates local access, high complexity, no required privileges, and no user interaction, with impact limited to availability.

Researcher notes

Evidence is sparse and centered on the advisory metadata. Do not broaden scope beyond buffered-reader before 1.1.5 without confirming dependency use and reachability. No exploit details or field exploitation are supported by the bundle.

Mitigation direction

  • Upgrade buffered-reader to version 1.1.5 or later where feasible.
  • Check vendor advisories for any project-specific remediation notes.
  • Rebuild and redeploy applications that vendor or statically link the crate.
  • Prioritize systems processing untrusted local files or automated batch inputs.

Validation and detection

  • Check Cargo.lock and SBOMs for buffered-reader versions earlier than 1.1.5.
  • Confirm whether vulnerable dependency paths are present in deployed builds.
  • Assess whether application code reaches affected reader functionality.
  • Run existing unit and regression tests after dependency upgrade.
  • Monitor crash telemetry for related panic patterns.
Prepared
Confidence
high
Sources
6

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-125: 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-2023-53161 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.9 (3.1)
Known Exploited
No
Published

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

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

Vulnerability scoring details

Base CVSS 3.1 score

2.9Low
CVSS 3.1 vector shape for CVE-2023-53161Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
sequoia-pgpbuffered-reader0, 1.1.0unaffected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.