This is an archived web site made available for research purposes. The web site is no longer maintained.

Qualifier Challenge - NRFIN_00041


Original Versions

Known Vulnerabilities

  • CWE-120 - Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
  • CWE-122 - Heap-based Buffer Overflow
  • CWE-129 - Improper Validation of Array Index
  • CWE-20 - Improper Input Validation
  • CWE-788 - Access of Memory Location After End of Buffer
  • CWEs are listed as indicated by the challenge author.

Scores

  • ForAllSecure: 3.84
  • DeepRed: 3.0
  • TECHx: 0.72
  • CSDS: 0.66
  • CodeJitsu: 0.04
  • Disekt: 0.0
  • Lekkertech: 0.0
  • Shellphish: 0.0
  • FuzzBOMB: 0.0
  • TrailofBits: 0.0
  • The maximum score for each challenge in CQE is 4, following the CQE Scoring Document.

Passed consensus evaluation

  • CodeJitsu - CB1
  • CSDS - CB1
  • ForAllSecure - CB1
  • Shellphish - CB1
  • TrailofBits - CB1

Proved a POV in reference challenge

Defense against reference POVs

  • CodeJitsu: 100.0% - CB1
  • ForAllSecure: 100.0% - CB1
  • TECHx: 100.0% - CB1
  • Shellphish: 100.0% - CB1
  • CSDS: 100.0% - CB1
  • TrailofBits: 100.0% - CB1
  • DeepRed: 100.0% - CB1

No submission

  • Eighth Place Team
  • Eleventh Place Team
  • Fifth Place Team - Finalist
  • First Place Team - Finalist
  • Fourth Place Team - Finalist
  • Ninth Place Team
  • Second Place Team - Finalist
  • Seventh Place Team - Finalist
  • Sixth Place Team - Finalist
  • Tenth Place Team
  • Third Place Team - Finalist
  • Thirteenth Place Team
  • Twelfth Place Team

All Submissions

Author Information

"Nick Davis" info@narfindustries.com

DARPA performer group

Narf Industries (NRFIN)

Description

This is an AIS message parser/decoder for the AIS Lite protocol(TM). The connecting client provides a proprerly structured AIS Lite sentence, and the service returns the English textual meaning of the encoded AIS Lite message.

AIS Lite is a protocol roughly based on NMEA 0183. When we say roughly based, we mean that we've refined it to remove all of the cruft that is not related to AIS messages. Additionally, we've removed all of the AIS messaging components that are rarely or never used.

To avoid concerns about this protocol being to similar to the actual NMEA sentence structure or AIS messages structure, we've taken the original NMEA/AIS protocols and altered their formats. So, the sentences used by this CB are not valid NMEA sentences and the encoded AIS messages are not valid AIS messages as decided by a standards-based NMEA/AIS protocol parsers.

Feature List

This service supports 3 AIS messages types (1, 4, 5). These are the most common, so we decided to ignore all others.

Message types 1 and 4 are transported in a single sentence, so they will receive the English translation as an immediate response. Message type 5 requires 2 sentences to transport it, so the first message will recieve a notification that it received a partial AIS message. The second sentence, will result in the English translation being returned.

Vulnerability

This CB has 1 vuln.

The vuln is a heap overflow that corrupts heap metadata, so calling free triggers SIGSEGV. The heap buffer for ss->ais_msg gets MAX_SETNENCE_LEN bytes of memory. And immediately following it in memory is the buffer for buf. Thus anything that can write more than MAX_SENTENCE_LEN chars to ss->ais_msg can overwrite the heap metadata between them. This occurs in sentence.c:104 on a type 5 message. The type 5 message requires 2 sentences to send the full message content. The second message may contain more chars than there is memory alloted, which the fieldncopy will directly copy into ss->ais_msg via the ss->p_ais_msg pointer.

Generic class of vulnerability

Classic heap buffer overflow

Null pointer dereference

Improper array bounds checking

Access memory beyond buffer

CWE classification

CWE-20 Improper Input Validation CWE-120 Buffer Copy without Checking Size of Input CWE-122 Heap-based Buffer Overflow CWE-129 Improper Validation of Array Index CWE-788 Access of Memory Location After End of Buffer

Challenges

  • The protocol is a very simple question/answer type protocol. However, the questions are very complex. The question is in the form of a string that has a defined format, length, and includes a checksum. Additionally, part of the question is encoded using 6bits per byte. The complexity of the string makes it difficult for an automated system to generate alternative input. This will make fuzzing incredibly difficult.

Curated by Lunge Technology, LLC. Questions or comments? Send us email