4. Was this attack addressed ?

Was this attack addressed ?

  • P

    See exploit-db listing here: https://www.exploit-db.com/exploits/31263/

    Was this addressed / fixed ?

    0

  • You're asking about a 1+ year-old exploit in an old version of pfSense?  Considering how they're usually right on top of security vulns, I would assume that it has long since been fixed.  If you need to confirm it, start reading through the various version release notes.  Too bad there's no CVE ID to match against.

    0
  • 2
    Banned

    Some basic linux/unix bugs took 10+ years to get fixed, so I would assume: valid question…

    0
  • T

    That's a bug in snort, not pfSense per se.

    I've done Nessus scans against pfSense that come up okay, so I wouldn't worry too much about this issue unless you have snort deployed.  Additionally, I recommend reviewing the snort change log and current version to see if this was addressed.

    0
 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy