CyberSecBulletin
CVE-2024-51979NVD status: Deferred

HL-L8260CDN: Stack-based Buffer Overflow

CVE-2024-51979 is a high-severity stack-based buffer overflow vulnerability in HL-L8260CDN from Brother Industries, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected HL-L8260CDN versions: 1.65(ZH) and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.15% chance of exploitation within 30 days, higher than 67% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of HL-L8260CDN you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Brother IndustriesHL-L8260CDN1.65(ZH) and earlierNot stated
Brother IndustriesHL-L8260CDW1.65(ZH) and earlierNot stated
Brother IndustriesHL-L8360CDW1.68(ZG) and earlierNot stated
Brother IndustriesHL-L8360CDWT1.68(ZG) and earlierNot stated
Brother IndustriesHL-L9310CDW1.68(ZG) and earlierNot stated
Brother IndustriesDCP-L8410CDWZK and earlierNot stated
Brother IndustriesMFC-L8610CDWZK and earlierNot stated
Brother IndustriesMFC-L8690CDWZK and earlierNot stated
Brother IndustriesMFC-L8900CDWZM and earlierNot stated
Brother IndustriesMFC-L9570CDWZM and earlierNot stated
Brother IndustriesMFC-L9577CDWZM and earlierNot stated
Brother IndustriesHL-L5210DN1.0 through 1.14(H)Not stated
Brother IndustriesHL-L5212DN1.14(H) and earlierNot stated
Brother IndustriesHL-L5215DN1.14(H) and earlierNot stated
Brother IndustriesHL-L5210DW1.0 through 1.14(H)Not stated
Brother IndustriesHL-L5210DWT1.14(H) and earlierNot stated
Brother IndustriesHL-L5212DW1.14(H) and earlierNot stated
Brother IndustriesHL-L5215DW1.14(H) and earlierNot stated
Brother IndustriesHL-L6210DW1.14(H) and earlierNot stated
Brother IndustriesHL-L6210DWT1.14(H) and earlierNot stated
Brother IndustriesHL-L6217DW1.14(H) and earlierNot stated
Brother IndustriesHL-L5218DN1.12(F) and earlierNot stated
Brother IndustriesHL-L5228DW1.12(F) and earlierNot stated
Brother IndustriesHL-L6310DW1.0 through 1.16(G)Not stated
Brother IndustriesHL-L6410DN1.16(G) and earlierNot stated

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (rapid7.com).

Official description

An authenticated attacker may trigger a stack based buffer overflow by performing a malformed request to either the HTTP service (TCP port 80), the HTTPS service (TCP port 443), or the IPP service (TCP port 631). The malformed request will contain an empty Origin header value and a malformed Referer header value. The Referer header value will trigger a stack based buffer overflow when the host value in the Referer header is processed and is greater than 64 bytes in length.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in HL-L8260CDN

All HL-L8260CDN vulnerabilities

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.