public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: celer@scrypt.net To: gnats-gnats@sourceware.cygnus.com Subject: gnats/169: gnatsd crashes/potential DOS attack. Date: Mon, 26 Mar 2001 11:24:00 -0000 [thread overview] Message-ID: <20010326191808.16762.qmail@sourceware.cygnus.com> (raw) >Number: 169 >Category: gnats >Synopsis: gnatsd crashes/potential DOS attack. >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Mar 26 11:24:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: celer@scrypt.net >Release: 3.113 >Organization: >Environment: Linux 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686 unknown >Description: gnatsd crashes when entering text for the "CHEK" command. There are a number of issues with this command. 1. There appears to be a problem with parsing the tags and making sure that the returned values are not null pointers. For example pr[RESPONSIBLE].value in edit.c line 399 is not checked before it is used. Other uses of pr[*].value are not checked either. Causing gnatsd to crash. When gnatsd crashes it leaves files in tmp. Potentially filling up the file system and causing a DOS attack. >How-To-Repeat: type this into gnatsd(either from the command prompt or from inetd) CHEK asfdsda This is not the only means to make this occur. You can also cause this by filling in some of the tags and not others. . and you will get CHEK 210 Ok. asfdsda . Segmentation fault (core dumped) >Fix: Check for null pointers in check_pr from edit.c >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-03-26 11:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010326191808.16762.qmail@sourceware.cygnus.com \ --to=celer@scrypt.net \ --cc=gnats-gnats@sourceware.cygnus.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).