[bug #63990] Fix a buffer overflow in warning.c.

2023-04-03 Thread Paul D. Smith
Update of bug #63990 (project make):

  Status:None => Fixed  
 Assigned to:None => psmith 
 Open/Closed:Open => Closed 
   Fixed Release:None => SCM
   Triage Status:None => Small Effort   

___

Follow-up Comment #3:

Fixed thanks Dmitry.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[bug #63990] Fix a buffer overflow in warning.c.

2023-04-02 Thread Dmitry Goncharov
Follow-up Comment #2, bug #63990 (project make):

There is already a test which tests this use case.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[bug #63990] Fix a buffer overflow in warning.c.

2023-04-02 Thread Dmitry Goncharov
Follow-up Comment #1, bug #63990 (project make):

Settings like .WARNINGS = bogus causes decode_warn_name to return wt_max.
decode_warn_actions then stores wt_max in type and the action at
data->actions[type] and touches beyond the size of data->actions.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[bug #63990] Fix a buffer overflow in warning.c.

2023-04-02 Thread Dmitry Goncharov
Additional Item Attachment, bug #63990 (project make):

File name: sv63990.fixSize:1 KB




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[bug #63990] Fix a buffer overflow in warning.c.

2023-04-02 Thread Dmitry Goncharov
URL:
  

 Summary: Fix a buffer overflow in warning.c.
   Group: make
   Submitter: dgoncharov
   Submitted: Sun 02 Apr 2023 06:38:21 PM UTC
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: SCM
Operating System: Any
   Fixed Release: None
   Triage Status: None


___

Follow-up Comments:


---
Date: Sun 02 Apr 2023 06:38:21 PM UTC By: Dmitry Goncharov 
.







___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/