rusticata/ldap-parser

LDAP parser written in pure Rust. Fast, zero-copy, safe.

LDAP Parser

A Lightweight Directory Access Protocol (LDAP) (RFC4511) parser, implemented with the nom parser combinator framework.

It is written in pure Rust, fast, and makes extensive use of zero-copy. A lot of care is taken to ensure security and safety of this crate, including design (recursion limit, defensive programming), tests, and fuzzing. It also aims to be panic-free.

The code is available on Github and is part of the Rusticata project.

Examples

Parsing an LDAP message (in BER format):

use ldap_parser::parse_ldap_message;
use ldap_parser::ldap::{MessageID, ProtocolOp, ProtocolOpTag};

static DATA: &[u8] = include_bytes!("../assets/message-search-request-01.bin");

let res = parse_ldap_message(DATA);
match res {
    Ok((rem, msg)) => {
        assert!(rem.is_empty());
        //
        assert_eq!(msg.message_id, MessageID(4));
        assert_eq!(msg.protocol_op.tag(), ProtocolOpTag::SearchRequest);
        match msg.protocol_op {
            ProtocolOp::SearchRequest(req) => {
                assert_eq!(req.base_object.0, "dc=rccad,dc=net");
            },
            _ => panic!("Unexpected message type"),
        }
    },
    _ => panic!("LDAP parsing failed: {:?}", res),
}

Changes

See CHANGELOG.md

License

Licensed under either of

• Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

ldap-parser's Issues

Abandon request not parsed correctly?

Hello Pierre,
While testing this parser, I discovered that the abandon request is (apparently) not parsed correctly.

If you run the following test:

#[test]
fn test_parse_abandon_request() {
    const DATA: &[u8] = &[
        0x30, 0x06, 0x02, 0x01, 0x06, 0x50, 0x01, 0x05
    ];

    let (rem, msg) = LdapMessage::from_ber(DATA).expect("parsing failed");
}

You will encounter this error:

parsing failed: Error(Ber(UnexpectedClass { expected: Some(ContextSpecific), actual: Application }))

I took the hex-encoded representation of this LDAP message from this link: https://ldap.com/ldapv3-wire-protocol-reference-abandon/ and I believe it should be correct.

Could you please confirm whether this is an issue or not?
Thanks!