ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 9120] Buildbot crash output: fuzz-2013-09-08-32595.pcap

Date: Tue, 24 Sep 2013 04:33:23 +0000

Comment # 9 on bug 9120 from
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > I think that suffers from the same problem, which is a dissector can't tell
> > > the type of the pointer without introspecting the stack somehow to tell the
> > > parent protocol.
> > 
> > Is there anything contained within pinfo that would (or could) indicate the
> > parent protocol?  pinfo->layer_names perhaps?
> 
> I didn't realize that field existed, although string comparisons are not
> ideal. It might be adaptable into a list of protocol ids though that would
> be useful.

Note that the list is only populated if tree(or something like that) for
performance reasons(?)

In epan/asn1.h asn1_ctx_t has a "signature"

#define ASN1_CTX_SIGNATURE 0x41435458  /* "ACTX" */

typedef struct _asn1_ctx_t {
  guint32 signature;
:

#define ROSE_CTX_SIGNATURE 0x524F5345  /* "ROSE" */

typedef struct _rose_ctx_t {
  guint32 signature;
:

Could something like that be used to ensure (assert)that the data is from the
right caller?


You are receiving this mail because:
  • You are watching all bug changes.