similar to: prs_mem_get: buffer overrun

Hello everyone, we try to use a server running linux in an NT-domain and get the error message given in the subject-line. More details from the logfile and smb.conf are given below. Can anyone give us a hint what the problem is? (Of course...) The problem is very urgent for us. Thanks a lot in advance. Helmut Rickel ================= smb.conf ======================== [global]

Hi all I am getting this error, when running the command below from my workstation: `--> sudo net rpc info -S SMBPDC [2005/08/17 14:33:16, 0] rpc_parse/parse_prs.c:prs_mem_get(537) prs_mem_get: reading data of size 14287078 would overrun buffer. However, if I run the same command from the PDC itself, then it's ok: . ldapsmb-pdc:~# net rpc info Domain Name: ILR Domain SID:

Hi I getting ready to migrate from samba 209 to 222. I'd like to use Windbind to authenticate against a WNT4 PDC. I understand, from reading the docs, how winbind works with respect to users and groups... it basically creates unix accounts using a given uid and gid range. I have a couple of questions... 1. I have existing unix user accounts and group accounts. Will I need to map these

I had posted about winbind picking the wrong domain to this list about a week ago and this was the problem I was still trying to solve when I must have messed something else up. SO! Winbind WAS working (even though it was picking the wrong domain) I re-ran smbpasswd -j LMC -r <our PDC> -U administrator I get prompted for the password, enter it and I am told that I joined the LMC

Hello I am running a net work with a NT4PDC a NT4 BDC and attent to add samba BDC. I am following the brief section 28 of the Samba-Howto collection for samba head/3.0. * Adding the samba server as a BDC from NT server manager seems OK * Getting, recording domain sid is ok (see below) > rpcclient NT4PDC -U Administrator password: > lsaquery domain IMAGERIE has sid blablabla > net

Every day I get emailed Logwatch reports with several entries of the following type. I've tried googling for these entries and found nothing that indicats if these represent any particular problem. We did not have these messages before and nothing really changed other than some RedHat updates. The system generally runs fine (~170 users) with only the occasional authentication glitch.

Hi, I'm running an 8E1 setup to an SS7 carrier. The setup works but when we start hitting the 80 active calls mark the link became unstable. I found a lot of the following messages afecting my d channel Jun 25 15:49:55 ostional kernel: [385661.368857] dahdi: HDLC Receiver overrun on channel TE4/0/1/31 (master=TE4/0/1/31) Im using TE410P dahdi-linux-2.4.1.2.tar.gz dahdi-tools-2.4.1.tar.gz

We recently upgraded our NT4 Domain to Win2k. We use Samba 2.0.7 running on Solaris 2.6 servers. We are getting buffer overuns in the log files when running 'domain_client_validate' which appears to be due to extensive group membership (SID History is not being used). Are there any patches/fixes available to get round this problem? Thankyou in anticipation. Regards, Rich Sprigg

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Stack buffer overflow in nmbd's logon == request processing. == == CVE ID#: CVE-2007-4572 == == Versions: Samba 3.0.0 - 3.0.26a (inclusive) == == Summary: Processing of specially crafted GETDC == mailslot requests can result in a

Asterisk Project Security Advisory - AST-2017-002 Product Asterisk Summary Buffer Overrun in PJSIP transaction layer Nature of Advisory Buffer Overrun/Crash Susceptibility Remote Unauthenticated Sessions Severity Critical

If the file size wasn't a multiple of 64KB, we could overwrite the next entry in the malloc arena so reading the initramfs would fail. Signed-off-by: Colin Watson <cjwatson at ubuntu.com> --- com32/gfxboot/gfxboot.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/com32/gfxboot/gfxboot.c b/com32/gfxboot/gfxboot.c index dd4d641..0fbfadd 100644 ---

Hello, Our UC-KLEE tool discovered a memcpy() read overrun bug in dg_dispatch_as_host() (drivers/misc/vmw_vmci/vmci_datagram.c). This bug may allow a malicious user to leak private kernel heap data across the VMware VMCI interface (in a nearly identical fashion to the OpenSSL Heartbleed vulnerability from 2014), but the impact is probably minimal since this interface is only used for local

Hello, Our UC-KLEE tool discovered a memcpy() read overrun bug in dg_dispatch_as_host() (drivers/misc/vmw_vmci/vmci_datagram.c). This bug may allow a malicious user to leak private kernel heap data across the VMware VMCI interface (in a nearly identical fashion to the OpenSSL Heartbleed vulnerability from 2014), but the impact is probably minimal since this interface is only used for local

Hello, I've observed in some tests that getValueTypeList() is sometimes called with type MVT::iPTR. There is a discrepancy between the size of the array VTs and the use in getTypeValueList(). The array is allocated with space for elements up to LAST_VALUE_TYPE and iPTR is defined after it. The enumerator value of iPTR is between LAST_VALUE_TYPE and LastSimpleValueType. For this reason the

Hi Duncan, I've modified my backend such that the function isn't called anymore with iPTR. I still think that if iPTR is an invalid input to getValueTypeList() that the function should have at least an assert checking that. Thanks, Javier Hi Javier, > I've observed in some tests that getValueTypeList() is sometimes called > with type MVT::iPTR. I think this is a bug,

Hi Javier, > I’ve modified my backend such that the function isn’t called anymore > with iPTR. I still think that if iPTR is an invalid input to > getValueTypeList() that the function should have at least an assert > checking that. I agree - please post a patch adding one. Ciao, Duncan.

Hello, The attached patch is to add an assert to getValueTypeList() to verify that for simple value types their value is NOT between MAX_ALLOWED_VALUETYPE and LastSimpleValueType (inclusive) as this causes a buffer overrun. Thanks, Javier -----Original Message----- From: Duncan Sands [mailto:baldrick at free.fr] Sent: Tuesday, April 27, 2010 5:07 AM To: Martinez, Javier E Cc: LLVM Developers

Hello All, I've just been made aware of Asterisk and have installed it. Things seem to be working: I can dial from the console the internal numbers and hear the answerphone messages and do other interesting stuff. however when I hangup the call I see a continuous stream of messages saying "Sound: Recording overrun" appear on ALL my linux consoles and I can't see what I'm

Hi, When I dial into asterisk I set it up in extensions.conf so it will play some messages, but when I dial in asterisk picks up but I hear no sound. There is moments of silence where the audio should be playing but I get nothing. I checked /var/log/messages to see what was wrong and I got the following error: Jun 29 20:46:33 eclipse kernel: Sound: Recording overrun Does this mean

When a forwarding specification ending in a slash ('\\') is used, the function "parse_fwd_field" jumps over the '\0' char marking the end of the string and keeps processing. This patch checks for that condition. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-buffer-overrun.patch Type: application/text Size: 850 bytes Desc: