T-021: libspf2 DNS TXT Vulnerability


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) T-021: libspf2 DNS TXT Vulnerability
# 1  
Old 11-13-2008
T-021: libspf2 DNS TXT Vulnerability

libspf2 contains a buffer overflow vulnerability in code that parses DNS TXT records. An SPF record is a DNS Resource Record (RR) that declares which hosts are, and are not, authorized to use a domain name for the "HELO" and "MAIL FROM" identities. The risk is MEDIUM. This vulnerability could allow an unauthenticated, remote attacker to execute arbitrary code on a system running libspf2.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

In BIND 9.3 DNS trying to get past the 256 char limit in SPF TXT records

One way I was told to do was incase strings in quotes. But I was given this option if I can get it to work. Will this work for splitting up SPF records? I am try to make bx.example.com reference spf.eu.***, spfa.eu.***, spfb.eu.***, and spfc.eu.***. spf.eu.example.com 3600 IN TXT "v=spf1... (0 Replies)
Discussion started by: tmanx
0 Replies
Login or Register to Ask a Question
avahi.service(5)						File Formats Manual						  avahi.service(5)

NAME
avahi.service - avahi-daemon static service file SYNOPSIS
/etc/avahi/services/*.service DESCRIPTION
/etc/avahi/services/*.service are XML fragments containing static DNS-SD service data. Every service file can contain multiple service def- initions which share the same name. This is useful for publishing service data for services which implement multiple protocols. (i.e. a printer implementing _ipp._tcp and _printer._tcp) XML TAGS
<service-group> The document tag of avahi service files. Should contain one <name> and one or more <service> elements. <name replace-wildcards="yes|no"> The service name. If replace-wildcards is "yes", any occurence of the string "%h" will be replaced by the local host name. This can be used for service names like "Remote Terminal on %h". If replace-wildcards is not specified, defaults to "no". <service protocol="ipv4|ipv6|any"> Contains the service information for exactly one service type. Should contain one <type> and one <port> element. Optionally it may contain one <domain-name>, one <host-name>, any number of <subtype> and any number of <txt-record> elements. The attribute protocol specifies the protocol to advertise the service on. If any is used (which is the default), the service will be adver- tised on both IPv4 and IPv6. <type> Contains the DNS-SD service type for this service. e.g. "_http._tcp". <subtype> Contains an additional DNS-SD service subtype for this service. e.g. "_anon._sub._ftp._tcp". <domain-name> The domain name this service should be registered. If omited defaults to the default domain of the avahi daemon. (probably .local) <host-name> The host name of the host that provides this service. This should be a host that is resolvable by multicast or unicast DNS. Please note that you need to specify a fully-qualified domain name (FQDN) here, i.e. .local is not appended implicitly! The host name doesn't need to be part of the domain specified in <domain-name>. See avahi.hosts(5) for more information how to publish additional host name mappings. <port> The IP port number the service listens on. <txt-record> DNS-SD TXT record data. AUTHORS
The Avahi Developers <avahi (at) lists (dot) freedesktop (dot) org>; Avahi is available from http://avahi.org/ SEE ALSO
avahi-daemon(8), avahi.hosts(5) COMMENTS
This man page was written using xml2man(1) by Oliver Kurth. Manuals User avahi.service(5)