Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Google] Segfault using network_monitor on Ubuntu, despite Wiki's Ubuntu modification #7

Closed
Fitblip opened this issue Apr 13, 2012 · 1 comment
Closed

[Google] Segfault using network_monitor on Ubuntu, despite Wiki's Ubuntu modification #7

Fitblip opened this issue Apr 13, 2012 · 1 comment
Assignees
@Fitblip
Labels
Bug Invalid OldVersion

Comments

@Fitblip
Copy link
Member

Fitblip commented Apr 13, 2012

What steps will reproduce the problem?

  1. Modifiyng pedrpc.py according to
    http://code.google.com/p/sulley/wiki/KnownBugs,
  2. Using attached files sip.py and requests/sip_data.py,
  3. Creating the folder audits/sip/,
  4. Running :
    3a. sudo python network_monitor.py -d 1 -f "src or dst port 5060" -P
    audits/sip
    3b. python sip.py

What is the expected output? What do you see instead?
A segmentation fault happens !

What version of the product are you using? On what operating system?
I am using the last cvs version (on the 2008-06-06, 16h16).
My system is an Ubuntu lenny/sid, 2.6.24-16-generic.
If you have any idea, please help me :)

Attachments:
sip.py & sip_data.py
@ghost ghost assigned Fitblip Apr 13, 2012
@Fitblip
Copy link
Member Author

Fitblip commented Sep 15, 2012

Super outdated version, no traceback, no better info. Closing.

@Fitblip Fitblip closed this as completed Sep 15, 2012
jtpereyda pushed a commit to jtpereyda/sulley that referenced this issue Oct 17, 2015
Merge pull request OpenRCE#7 in SEG/sulley-sel from ~JOSHPERE/sulley-…
7106555 
…sel:ipv4-checksum to develop

Merging results of FUZZ-24.

* commit '7553fad5fd9b5176198088ccb027d8159b4edb3a':
  Reverting a leftover debugging change.
  Fix: Block.render() was not using the checksum value computed after processing callbacks.
  FUZZ-24 Cleaning up and comments.
  Checksum loop-protection should now work when the target is a grandparent, or when multiple self-referential blocks are in the same parent block.
  The checksum now always tries to exclude itself from calculations, meaning that it should return a more consistent value. Previously, the checksum could be rendered incorrectly if render() was called twice (which apparently happens in the Sulley internals).
  Cleaned up and commented code.
  IPv4 checksums working. Next up: clean up changes; drop block_callback().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Fitblip Fitblip

Labels
Bug Invalid OldVersion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Fitblip