Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler. Number of rules (primarily dangerous function names) in C/C++ ruleset: 223 Examining data/fort-validator-1.4.2/src/address.c Examining data/fort-validator-1.4.2/src/address.h Examining data/fort-validator-1.4.2/src/algorithm.c Examining data/fort-validator-1.4.2/src/algorithm.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ANY.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ANY.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASID.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASID.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASId.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASId.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdOrRange.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdOrRange.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdentifierChoice.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdentifierChoice.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdentifiers.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASIdentifiers.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASRange.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ASRange.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/AlgorithmIdentifier.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/AlgorithmIdentifier.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeType.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeType.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeTypeAndValue.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeTypeAndValue.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeValue.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/AttributeValue.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/BOOLEAN.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/BOOLEAN.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/BinarySigningTime.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/BinarySigningTime.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/BinaryTime.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/BinaryTime.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSAttribute.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSAttribute.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSAttributeValue.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSAttributeValue.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSSubjectKeyIdentifier.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSSubjectKeyIdentifier.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSVersion.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CMSVersion.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateList.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateList.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateSerialNumber.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateSerialNumber.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateSet.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/CertificateSet.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentInfo.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentInfo.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentType.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentType.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentTypePKCS7.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ContentTypePKCS7.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Countersignature.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Countersignature.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/DigestAlgorithmIdentifier.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/DigestAlgorithmIdentifier.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/DigestAlgorithmIdentifiers.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/DigestAlgorithmIdentifiers.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/DistinguishedName.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/DistinguishedName.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/EncapsulatedContentInfo.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/EncapsulatedContentInfo.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/EncapsulatedContentInfoPKCS7.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/EncapsulatedContentInfoPKCS7.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Extension.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Extension.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Extensions.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Extensions.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/FileAndHash.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/FileAndHash.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IA5String.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IA5String.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddrBlocks.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddrBlocks.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddress.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddress.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressChoice.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressChoice.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressFamily.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressFamily.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressOrRange.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressOrRange.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressRange.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IPAddressRange.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/IssuerAndSerialNumber.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/IssuerAndSerialNumber.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Manifest.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Manifest.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/MessageDigest.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/MessageDigest.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/NULL.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/NULL.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Name.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Name.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OPEN_TYPE.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OPEN_TYPE.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/OPEN_TYPE_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OtherRevocationInfoFormat.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/OtherRevocationInfoFormat.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/RDNSequence.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/RDNSequence.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ROAIPAddress.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ROAIPAddress.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ROAIPAddressFamily.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ROAIPAddressFamily.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/RelativeDistinguishedName.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/RelativeDistinguishedName.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/RevocationInfoChoice.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/RevocationInfoChoice.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/RevocationInfoChoices.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/RevocationInfoChoices.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/RouteOriginAttestation.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/RouteOriginAttestation.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignatureAlgorithmIdentifier.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignatureAlgorithmIdentifier.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignatureValue.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignatureValue.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedAttributes.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedAttributes.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedData.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedData.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedDataPKCS7.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignedDataPKCS7.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerIdentifier.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerIdentifier.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerInfo.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerInfo.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerInfos.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SignerInfos.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/SigningTime.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/SigningTime.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/TBSCertList.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/TBSCertList.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Time.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Time.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/UTCTime.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/UTCTime.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/UnsignedAttributes.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/UnsignedAttributes.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/Version.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/Version.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_SEQUENCE_OF.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_SEQUENCE_OF.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_SET_OF.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_SET_OF.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_application.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_application.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_bit_data.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_bit_data.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_codecs.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_codecs_prim.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_codecs_prim.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_internal.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_internal.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_ioc.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_random_fill.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_random_fill.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/asn_system.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_decoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_decoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_length.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_length.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_tag.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_tag.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_CHOICE.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_CHOICE.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_CHOICE_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE_OF.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE_OF.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF_oer.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_TYPE.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constr_TYPE.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/constraints.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/constraints.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/der_encoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/der_encoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_decoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_decoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_encoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_encoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_support.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/oer_support.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_decoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_decoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_encoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_encoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_opentype.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_opentype.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_support.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/per_support.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_decoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_decoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_encoder.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_encoder.h Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_support.c Examining data/fort-validator-1.4.2/src/asn1/asn1c/xer_support.h Examining data/fort-validator-1.4.2/src/asn1/content_info.c Examining data/fort-validator-1.4.2/src/asn1/content_info.h Examining data/fort-validator-1.4.2/src/asn1/decode.c Examining data/fort-validator-1.4.2/src/asn1/decode.h Examining data/fort-validator-1.4.2/src/asn1/oid.c Examining data/fort-validator-1.4.2/src/asn1/oid.h Examining data/fort-validator-1.4.2/src/asn1/signed_data.c Examining data/fort-validator-1.4.2/src/asn1/signed_data.h Examining data/fort-validator-1.4.2/src/cert_stack.c Examining data/fort-validator-1.4.2/src/cert_stack.h Examining data/fort-validator-1.4.2/src/certificate_refs.c Examining data/fort-validator-1.4.2/src/certificate_refs.h Examining data/fort-validator-1.4.2/src/clients.c Examining data/fort-validator-1.4.2/src/clients.h Examining data/fort-validator-1.4.2/src/common.c Examining data/fort-validator-1.4.2/src/common.h Examining data/fort-validator-1.4.2/src/config.h Examining data/fort-validator-1.4.2/src/config/boolean.c Examining data/fort-validator-1.4.2/src/config/boolean.h Examining data/fort-validator-1.4.2/src/config/filename_format.c Examining data/fort-validator-1.4.2/src/config/filename_format.h Examining data/fort-validator-1.4.2/src/config/incidences.c Examining data/fort-validator-1.4.2/src/config/incidences.h Examining data/fort-validator-1.4.2/src/config/log_conf.c Examining data/fort-validator-1.4.2/src/config/log_conf.h Examining data/fort-validator-1.4.2/src/config/mode.c Examining data/fort-validator-1.4.2/src/config/mode.h Examining data/fort-validator-1.4.2/src/config/rrdp_conf.c Examining data/fort-validator-1.4.2/src/config/rrdp_conf.h Examining data/fort-validator-1.4.2/src/config/rsync_strategy.c Examining data/fort-validator-1.4.2/src/config/rsync_strategy.h Examining data/fort-validator-1.4.2/src/config/str.c Examining data/fort-validator-1.4.2/src/config/str.h Examining data/fort-validator-1.4.2/src/config/string_array.c Examining data/fort-validator-1.4.2/src/config/string_array.h Examining data/fort-validator-1.4.2/src/config/sync_strategy.c Examining data/fort-validator-1.4.2/src/config/sync_strategy.h Examining data/fort-validator-1.4.2/src/config/types.h Examining data/fort-validator-1.4.2/src/config/uint.c Examining data/fort-validator-1.4.2/src/config/uint.h Examining data/fort-validator-1.4.2/src/config/uint32.c Examining data/fort-validator-1.4.2/src/config/uint32.h Examining data/fort-validator-1.4.2/src/config/work_offline.c Examining data/fort-validator-1.4.2/src/config/work_offline.h Examining data/fort-validator-1.4.2/src/crypto/base64.c Examining data/fort-validator-1.4.2/src/crypto/base64.h Examining data/fort-validator-1.4.2/src/crypto/hash.c Examining data/fort-validator-1.4.2/src/crypto/hash.h Examining data/fort-validator-1.4.2/src/data_structure/array_list.h Examining data/fort-validator-1.4.2/src/data_structure/common.h Examining data/fort-validator-1.4.2/src/data_structure/uthash.h Examining data/fort-validator-1.4.2/src/data_structure/uthash_nonfatal.h Examining data/fort-validator-1.4.2/src/debug.c Examining data/fort-validator-1.4.2/src/debug.h Examining data/fort-validator-1.4.2/src/delete_dir_daemon.c Examining data/fort-validator-1.4.2/src/delete_dir_daemon.h Examining data/fort-validator-1.4.2/src/extension.c Examining data/fort-validator-1.4.2/src/extension.h Examining data/fort-validator-1.4.2/src/file.c Examining data/fort-validator-1.4.2/src/file.h Examining data/fort-validator-1.4.2/src/http/http.c Examining data/fort-validator-1.4.2/src/http/http.h Examining data/fort-validator-1.4.2/src/incidence/incidence.c Examining data/fort-validator-1.4.2/src/incidence/incidence.h Examining data/fort-validator-1.4.2/src/json_handler.c Examining data/fort-validator-1.4.2/src/json_handler.h Examining data/fort-validator-1.4.2/src/json_parser.c Examining data/fort-validator-1.4.2/src/json_parser.h Examining data/fort-validator-1.4.2/src/line_file.c Examining data/fort-validator-1.4.2/src/line_file.h Examining data/fort-validator-1.4.2/src/log.c Examining data/fort-validator-1.4.2/src/log.h Examining data/fort-validator-1.4.2/src/main.c Examining data/fort-validator-1.4.2/src/nid.c Examining data/fort-validator-1.4.2/src/nid.h Examining data/fort-validator-1.4.2/src/notify.c Examining data/fort-validator-1.4.2/src/notify.h Examining data/fort-validator-1.4.2/src/object/bgpsec.c Examining data/fort-validator-1.4.2/src/object/bgpsec.h Examining data/fort-validator-1.4.2/src/object/certificate.c Examining data/fort-validator-1.4.2/src/object/certificate.h Examining data/fort-validator-1.4.2/src/object/crl.c Examining data/fort-validator-1.4.2/src/object/crl.h Examining data/fort-validator-1.4.2/src/object/ghostbusters.c Examining data/fort-validator-1.4.2/src/object/ghostbusters.h Examining data/fort-validator-1.4.2/src/object/manifest.c Examining data/fort-validator-1.4.2/src/object/manifest.h Examining data/fort-validator-1.4.2/src/object/name.c Examining data/fort-validator-1.4.2/src/object/name.h Examining data/fort-validator-1.4.2/src/object/roa.c Examining data/fort-validator-1.4.2/src/object/roa.h Examining data/fort-validator-1.4.2/src/object/router_key.c Examining data/fort-validator-1.4.2/src/object/router_key.h Examining data/fort-validator-1.4.2/src/object/signed_object.c Examining data/fort-validator-1.4.2/src/object/signed_object.h Examining data/fort-validator-1.4.2/src/object/tal.c Examining data/fort-validator-1.4.2/src/object/tal.h Examining data/fort-validator-1.4.2/src/object/vcard.c Examining data/fort-validator-1.4.2/src/object/vcard.h Examining data/fort-validator-1.4.2/src/output_printer.c Examining data/fort-validator-1.4.2/src/output_printer.h Examining data/fort-validator-1.4.2/src/random.c Examining data/fort-validator-1.4.2/src/random.h Examining data/fort-validator-1.4.2/src/reqs_errors.c Examining data/fort-validator-1.4.2/src/reqs_errors.h Examining data/fort-validator-1.4.2/src/resource.c Examining data/fort-validator-1.4.2/src/resource.h Examining data/fort-validator-1.4.2/src/resource/asn.c Examining data/fort-validator-1.4.2/src/resource/asn.h Examining data/fort-validator-1.4.2/src/resource/ip4.c Examining data/fort-validator-1.4.2/src/resource/ip4.h Examining data/fort-validator-1.4.2/src/resource/ip6.c Examining data/fort-validator-1.4.2/src/resource/ip6.h Examining data/fort-validator-1.4.2/src/rpp.c Examining data/fort-validator-1.4.2/src/rpp.h Examining data/fort-validator-1.4.2/src/rrdp/db/db_rrdp.c Examining data/fort-validator-1.4.2/src/rrdp/db/db_rrdp.h Examining data/fort-validator-1.4.2/src/rrdp/db/db_rrdp_uris.c Examining data/fort-validator-1.4.2/src/rrdp/db/db_rrdp_uris.h Examining data/fort-validator-1.4.2/src/rrdp/rrdp_loader.c Examining data/fort-validator-1.4.2/src/rrdp/rrdp_loader.h Examining data/fort-validator-1.4.2/src/rrdp/rrdp_objects.c Examining data/fort-validator-1.4.2/src/rrdp/rrdp_objects.h Examining data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c Examining data/fort-validator-1.4.2/src/rrdp/rrdp_parser.h Examining data/fort-validator-1.4.2/src/rsync/rsync.c Examining data/fort-validator-1.4.2/src/rsync/rsync.h Examining data/fort-validator-1.4.2/src/rtr/db/db_table.c Examining data/fort-validator-1.4.2/src/rtr/db/db_table.h Examining data/fort-validator-1.4.2/src/rtr/db/delta.c Examining data/fort-validator-1.4.2/src/rtr/db/delta.h Examining data/fort-validator-1.4.2/src/rtr/db/roa.c Examining data/fort-validator-1.4.2/src/rtr/db/roa.h Examining data/fort-validator-1.4.2/src/rtr/db/vrp.h Examining data/fort-validator-1.4.2/src/rtr/db/vrps.c Examining data/fort-validator-1.4.2/src/rtr/db/vrps.h Examining data/fort-validator-1.4.2/src/rtr/err_pdu.c Examining data/fort-validator-1.4.2/src/rtr/err_pdu.h Examining data/fort-validator-1.4.2/src/rtr/pdu.c Examining data/fort-validator-1.4.2/src/rtr/pdu.h Examining data/fort-validator-1.4.2/src/rtr/pdu_handler.c Examining data/fort-validator-1.4.2/src/rtr/pdu_handler.h Examining data/fort-validator-1.4.2/src/rtr/pdu_sender.c Examining data/fort-validator-1.4.2/src/rtr/pdu_sender.h Examining data/fort-validator-1.4.2/src/rtr/pdu_serializer.c Examining data/fort-validator-1.4.2/src/rtr/pdu_serializer.h Examining data/fort-validator-1.4.2/src/rtr/primitive_reader.c Examining data/fort-validator-1.4.2/src/rtr/primitive_reader.h Examining data/fort-validator-1.4.2/src/rtr/primitive_writer.c Examining data/fort-validator-1.4.2/src/rtr/primitive_writer.h Examining data/fort-validator-1.4.2/src/rtr/rtr.c Examining data/fort-validator-1.4.2/src/rtr/rtr.h Examining data/fort-validator-1.4.2/src/slurm/db_slurm.c Examining data/fort-validator-1.4.2/src/slurm/db_slurm.h Examining data/fort-validator-1.4.2/src/slurm/slurm_loader.c Examining data/fort-validator-1.4.2/src/slurm/slurm_loader.h Examining data/fort-validator-1.4.2/src/slurm/slurm_parser.c Examining data/fort-validator-1.4.2/src/slurm/slurm_parser.h Examining data/fort-validator-1.4.2/src/sorted_array.c Examining data/fort-validator-1.4.2/src/sorted_array.h Examining data/fort-validator-1.4.2/src/state.c Examining data/fort-validator-1.4.2/src/state.h Examining data/fort-validator-1.4.2/src/str_token.c Examining data/fort-validator-1.4.2/src/str_token.h Examining data/fort-validator-1.4.2/src/thread_var.c Examining data/fort-validator-1.4.2/src/thread_var.h Examining data/fort-validator-1.4.2/src/updates_daemon.c Examining data/fort-validator-1.4.2/src/updates_daemon.h Examining data/fort-validator-1.4.2/src/uri.c Examining data/fort-validator-1.4.2/src/uri.h Examining data/fort-validator-1.4.2/src/validation_handler.c Examining data/fort-validator-1.4.2/src/validation_handler.h Examining data/fort-validator-1.4.2/src/visited_uris.c Examining data/fort-validator-1.4.2/src/visited_uris.h Examining data/fort-validator-1.4.2/src/xml/relax_ng.c Examining data/fort-validator-1.4.2/src/xml/relax_ng.h Examining data/fort-validator-1.4.2/src/config.c Examining data/fort-validator-1.4.2/test/address_test.c Examining data/fort-validator-1.4.2/test/client_test.c Examining data/fort-validator-1.4.2/test/http_test.c Examining data/fort-validator-1.4.2/test/impersonator.c Examining data/fort-validator-1.4.2/test/line_file_test.c Examining data/fort-validator-1.4.2/test/rsync_test.c Examining data/fort-validator-1.4.2/test/rtr/db/db_table_test.c Examining data/fort-validator-1.4.2/test/rtr/db/rtr_db_impersonator.c Examining data/fort-validator-1.4.2/test/rtr/db/vrps_test.c Examining data/fort-validator-1.4.2/test/rtr/pdu_handler_test.c Examining data/fort-validator-1.4.2/test/rtr/pdu_test.c Examining data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c Examining data/fort-validator-1.4.2/test/rtr/stream.c Examining data/fort-validator-1.4.2/test/rtr/stream.h Examining data/fort-validator-1.4.2/test/tal_test.c Examining data/fort-validator-1.4.2/test/vcard_test.c Examining data/fort-validator-1.4.2/test/xml_test.c FINAL RESULTS: data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c:148:11: [4] (format) snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. ret = snprintf(scratch, sizeof(scratch), "%"PRIu32".%"PRIu32, arc0, arc1); data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c:168:19: [4] (format) snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. ret = snprintf(scratch, sizeof(scratch), ".%" PRIu32, arc); data/fort-validator-1.4.2/src/asn1/asn1c/asn_internal.c:16:17: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. wrote = vsnprintf(buf, buf_size, fmt, args); data/fort-validator-1.4.2/src/asn1/asn1c/asn_internal.h:58:3: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. fprintf(stderr, fmt, ##args); \ data/fort-validator-1.4.2/src/asn1/asn1c/asn_system.h:34:10: [4] (format) snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. #define snprintf _snprintf data/fort-validator-1.4.2/src/asn1/asn1c/asn_system.h:34:19: [4] (format) _snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. #define snprintf _snprintf data/fort-validator-1.4.2/src/asn1/asn1c/asn_system.h:35:10: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. #define vsnprintf _vsnprintf data/fort-validator-1.4.2/src/asn1/asn1c/asn_system.h:89:57: [4] (format) printf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. #define CC_PRINTFLIKE(fmt, var) CC_ATTRIBUTE(format(printf, fmt, var)) data/fort-validator-1.4.2/src/asn1/asn1c/constr_TYPE.c:77:2: [4] (format) vfprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. vfprintf(stderr, fmt, ap); data/fort-validator-1.4.2/src/asn1/asn1c/constraints.c:53:9: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vlen = vsnprintf(arg->errbuf, maxlen, fmt, ap); data/fort-validator-1.4.2/src/common.c:118:2: [4] (buffer) strcat: Does not check for buffer overflows when concatenating to destination [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or snprintf (warning: strncat is easily misused). strcat(tmp, file_name); data/fort-validator-1.4.2/src/common.c:465:2: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). strcpy(local + offset, repository); data/fort-validator-1.4.2/src/common.c:472:3: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). strcpy(local + offset, workspace); data/fort-validator-1.4.2/src/config.c:758:2: [4] (format) printf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. printf(PACKAGE_STRING "\n"); data/fort-validator-1.4.2/src/data_structure/uthash.h:525:29: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. #define HASH_OOPS(...) do { fprintf(stderr,__VA_ARGS__); exit(-1); } while (0) data/fort-validator-1.4.2/src/http/http.c:199:2: [4] (buffer) strcat: Does not check for buffer overflows when concatenating to destination [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or snprintf (warning: strncat is easily misused). strcat(tmp_file, tmp_suffix); data/fort-validator-1.4.2/src/log.c:199:2: [4] (format) vfprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. vfprintf(lvl->stream, format, args); data/fort-validator-1.4.2/src/log.c:203:3: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. fprintf(lvl->stream, COLOR_RESET); data/fort-validator-1.4.2/src/log.c:225:2: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(msg, MSG_LEN, format, args); data/fort-validator-1.4.2/src/log.c:272:2: [4] (format) vfprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. vfprintf(lvl->stream, format, args); data/fort-validator-1.4.2/src/log.h:30:55: [4] (format) printf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. #define CHECK_FORMAT(str, args) __attribute__((format(printf, str, args))) data/fort-validator-1.4.2/src/rsync/rsync.c:254:2: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execvp(args[0], args); data/fort-validator-1.4.2/src/xml/relax_ng.c:20:2: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(log_msg, LOG_MSG_LEN, msg, args); \ data/fort-validator-1.4.2/test/line_file_test.c:41:3: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). strcpy(long_string + i * SENTENCE_LEN, SENTENCE); data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:123:10: [3] (buffer) getenv: Environment variables are untrustable input if they can be set by an attacker. They can have any content and length, and the same variable can be set more than once (CWE-807, CWE-20). Check environment variables carefully before using them. tzold = getenv("TZ"); \ data/fort-validator-1.4.2/src/asn1/asn1c/asn_random_fill.c:51:38: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation (CWE-327). Use a more secure technique for acquiring random values. value = (value << 24) | (random() % 0xffffff); data/fort-validator-1.4.2/src/common.c:119:13: [3] (buffer) realpath: This function does not protect against buffer overflows, and some implementations can overflow internally (CWE-120/CWE-785!). Ensure that the destination buffer is at least of size MAXPATHLEN, andto protect against implementation problems, the input argument should also be checked to ensure it is no larger than MAXPATHLEN. fullpath = realpath(tmp, NULL); data/fort-validator-1.4.2/src/config.c:1122:16: [3] (buffer) getopt_long: Some older implementations do not protect against internal buffer overflows (CWE-120, CWE-20). Check implementation on installation, or limit the size of all string inputs. while ((opt = getopt_long(argc, argv, short_opts, long_opts, NULL)) data/fort-validator-1.4.2/src/random.c:13:2: [3] (random) srandom: This function is not sufficiently random for security-related functions such as key and nonce creation (CWE-327). Use a more secure technique for acquiring random values. srandom(time(NULL)); data/fort-validator-1.4.2/src/random.c:32:7: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation (CWE-327). Use a more secure technique for acquiring random values. x = random(); data/fort-validator-1.4.2/src/address.c:178:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result->addr, str->buf, str->size); data/fort-validator-1.4.2/src/address.c:215:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result->addr, str->buf, str->size); data/fort-validator-1.4.2/src/address.c:462:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET_ADDRSTRLEN]; data/fort-validator-1.4.2/src/address.c:475:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/asn1/asn1c/ANY.c:175:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arg->buffer + arg->offset, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c:86:14: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static const char *_bit_pattern[16] = { data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c:96:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[128]; data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c:123:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(p + 0, _bit_pattern[v >> 4], 4); data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c:124:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(p + 4, _bit_pattern[v & 0x0f], 4); data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING.c:157:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[64]; data/fort-validator-1.4.2/src/asn1/asn1c/BIT_STRING_oer.c:74:13: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(buf, ptr, expected_length); data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:38:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. return memcpy(result, tm, sizeof(struct tm)); data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:45:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. return memcpy(result, tm, sizeof(struct tm)); data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:120:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char tzoldbuf[64]; \ data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:127:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. tzold = memcpy(tzoldbuf, tzold, tzlen + 1); \ data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:131:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. if(tzold) memcpy(tzold, dupptr, tzlen + 1); \ data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:316:3: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[32]; data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER.c:131:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[32]; data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER_oer.c:77:9: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(st->buf + msb, ptr, req_bytes); data/fort-validator-1.4.2/src/asn1/asn1c/INTEGER_oer.c:90:9: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(st->buf, ptr, req_bytes); data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c:136:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[32]; data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c:366:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arcbuf, b, result_len); data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:113:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(st->buf + st->size, bufptr, _bs); \ data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:365:4: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[2][32]; data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:603:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[16 * 3 + 4]; data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:1653:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[16 * 3 + 4]; data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:1789:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(buf, str, len); data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING_oer.c:87:13: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(buf, ptr, expected_length); data/fort-validator-1.4.2/src/asn1/asn1c/UTCTime.c:134:3: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[32]; data/fort-validator-1.4.2/src/asn1/asn1c/UTCTime.c:155:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[24]; /* "AAMMJJhhmmss+hhmm" + cushion */ data/fort-validator-1.4.2/src/asn1/asn1c/UTCTime.c:166:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(gt.buf + 2, st->buf, st->size); data/fort-validator-1.4.2/src/asn1/asn1c/asn_application.c:72:9: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy((char *)key->buffer + key->computed_size, data, size); data/fort-validator-1.4.2/src/asn1/asn1c/asn_application.c:108:9: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy((char *)key->buffer + key->computed_size, data, size); data/fort-validator-1.4.2/src/asn1/asn1c/asn_bit_data.c:26:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(bytes, data, size_bytes); data/fort-validator-1.4.2/src/asn1/asn1c/asn_bit_data.c:38:9: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char buf[2][32]; data/fort-validator-1.4.2/src/asn1/asn1c/asn_codecs_prim.c:67:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(st->buf, buf_ptr, length); data/fort-validator-1.4.2/src/asn1/asn1c/asn_codecs_prim.c:167:31: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. assert(chunk_size && ((const char *)chunk_buf)[0] == 0x3c); data/fort-validator-1.4.2/src/asn1/asn1c/asn_internal.c:6:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char scratch[64]; data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_tag.c:63:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[sizeof("[APPLICATION ]") + 32]; data/fort-validator-1.4.2/src/asn1/asn1c/ber_tlv_tag.c:95:9: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char buf[sizeof("[APPLICATION ]") + 32]; data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:854:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>0?((const char *)ptr)[0]:'.', data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:855:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>1?((const char *)ptr)[1]:'.', data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:856:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>2?((const char *)ptr)[2]:'.', data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:857:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>3?((const char *)ptr)[3]:'.', data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:858:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>4?((const char *)ptr)[4]:'.', data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:859:19: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. size>5?((const char *)ptr)[5]:'.'); data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:246:28: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. if(LEFT > 0 && ((const char *)ptr)[0] != 0) { data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:253:15: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. if(((const char *)ptr)[0] == 0 data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:254:15: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. && ((const char *)ptr)[1] == 0) { data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:298:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(el_buf->buf + el_buf->length, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:674:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy((char *)t->buffer + t->offset, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/constraints.c:69:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arg->errbuf, "<broken vsnprintf>", arg->errlen); data/fort-validator-1.4.2/src/asn1/asn1c/der_encoder.c:41:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arg->buffer, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/oer_decoder.c:142:13: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(buf, ptr, expected_length); data/fort-validator-1.4.2/src/asn1/asn1c/oer_encoder.c:38:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arg->buffer, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/per_encoder.c:63:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(arg->buffer, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/per_encoder.c:109:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(((char *)arg->buffer) + arg->length, buffer, size); data/fort-validator-1.4.2/src/asn1/asn1c/xer_encoder.c:84:13: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(new_buf, xb->buffer, xb->buffer_size); data/fort-validator-1.4.2/src/asn1/asn1c/xer_encoder.c:91:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(xb->buffer + xb->buffer_size, buffer, size); data/fort-validator-1.4.2/src/asn1/decode.c:21:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char error_msg[256]; data/fort-validator-1.4.2/src/common.c:206:9: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). file = fopen(location, "rb"); data/fort-validator-1.4.2/src/crypto/base64.c:156:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(str_copy, str_encoded, encoded_len); data/fort-validator-1.4.2/src/crypto/base64.c:224:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, base, len); data/fort-validator-1.4.2/src/crypto/hash.c:126:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char actual[EVP_MAX_MD_SIZE]; data/fort-validator-1.4.2/src/crypto/hash.c:167:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char actual[EVP_MAX_MD_SIZE]; data/fort-validator-1.4.2/src/crypto/hash.c:218:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char actual[EVP_MAX_MD_SIZE]; data/fort-validator-1.4.2/src/crypto/hash.c:257:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(src, str, strlen(str)); data/fort-validator-1.4.2/src/file.c:14:9: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). file = fopen(file_name, mode); data/fort-validator-1.4.2/src/http/http.c:22:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char errbuf[CURL_ERROR_SIZE]; data/fort-validator-1.4.2/src/line_file.c:29:16: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). lfile->file = fopen(file_name, "r"); data/fort-validator-1.4.2/src/log.c:177:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char time_buff[20]; data/fort-validator-1.4.2/src/log.c:219:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char msg[MSG_LEN]; data/fort-validator-1.4.2/src/log.c:247:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char time_buff[20]; data/fort-validator-1.4.2/src/object/certificate.c:223:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, cert->buf, cert->size); data/fort-validator-1.4.2/src/object/certificate.c:1328:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, ski->data, ski->length); data/fort-validator-1.4.2/src/object/certificate.c:1386:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[2]; data/fort-validator-1.4.2/src/object/certificate.c:1400:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(data, ku->data, ku->length); data/fort-validator-1.4.2/src/object/name.c:36:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(result, data->data, data->length); data/fort-validator-1.4.2/src/object/router_key.c:9:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(key->ski, ski, RK_SKI_LEN); data/fort-validator-1.4.2/src/object/router_key.c:10:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(key->spk, spk, RK_SPKI_LEN); data/fort-validator-1.4.2/src/object/router_key.h:28:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char ski[RK_SKI_LEN]; data/fort-validator-1.4.2/src/object/router_key.h:30:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char spk[RK_SPKI_LEN]; data/fort-validator-1.4.2/src/object/tal.c:270:4: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result[offset], buf, fread_result - 1); data/fort-validator-1.4.2/src/object/tal.c:278:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result[offset], buf, eol - buf + 1); data/fort-validator-1.4.2/src/object/tal.c:282:4: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result[offset], eol + 1, data/fort-validator-1.4.2/src/output_printer.c:11:8: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char addr_buf[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/output_printer.c:14:59: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). load_output_file(char const *output, FILE **result, bool *fopen) data/fort-validator-1.4.2/src/output_printer.c:90:46: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). open_file(char const *loc, FILE **out, bool *fopen) data/fort-validator-1.4.2/src/output_printer.c:94:37: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). error = load_output_file(loc, out, fopen); data/fort-validator-1.4.2/src/output_printer.c:109:7: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). bool fopen; data/fort-validator-1.4.2/src/output_printer.c:113:52: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). error = open_file(config_get_output_roa(), &out, &fopen); data/fort-validator-1.4.2/src/output_printer.c:119:6: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). if (fopen) data/fort-validator-1.4.2/src/output_printer.c:129:7: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). bool fopen; data/fort-validator-1.4.2/src/output_printer.c:133:55: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). error = open_file(config_get_output_bgpsec(), &out, &fopen); data/fort-validator-1.4.2/src/output_printer.c:139:6: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). if (fopen) data/fort-validator-1.4.2/src/rrdp/db/db_rrdp.c:75:3: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(ptr, "%02X", hash[i]); data/fort-validator-1.4.2/src/rrdp/rrdp_objects.c:192:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(elem->doc_data.hash, hash, hash_len); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:196:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&result[offset], tmp, buf_len); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:292:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, xml_value, xmlStrlen(xml_value)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:332:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buf[2]; data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:359:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(buf, xml_cur, 2); data/fort-validator-1.4.2/src/rsync/rsync.c:225:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(copy_args + 1, config_args->array, data/fort-validator-1.4.2/src/rsync/rsync.c:247:21: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. handle_child_thread(char **args, int fds[2][2]) data/fort-validator-1.4.2/src/rsync/rsync.c:316:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[4096]; data/fort-validator-1.4.2/src/rtr/db/delta.c:21:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char ski[RK_SKI_LEN]; data/fort-validator-1.4.2/src/rtr/db/delta.c:23:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char spk[RK_SPKI_LEN]; data/fort-validator-1.4.2/src/rtr/db/delta.c:138:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(delta.ski, key->ski, RK_SKI_LEN); data/fort-validator-1.4.2/src/rtr/db/delta.c:139:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(delta.spk, key->spk, RK_SPKI_LEN); data/fort-validator-1.4.2/src/rtr/db/delta.c:228:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(delta.router_key.ski, d->ski, RK_SKI_LEN); data/fort-validator-1.4.2/src/rtr/db/delta.c:229:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(delta.router_key.spk, d->spk, RK_SPKI_LEN); data/fort-validator-1.4.2/src/rtr/db/vrps.c:240:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, start, db->len * sizeof(struct delta_group)); data/fort-validator-1.4.2/src/rtr/pdu.c:111:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char hdr_bytes[RTRPDU_HDR_LEN]; data/fort-validator-1.4.2/src/rtr/pdu.c:130:3: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/rtr/pdu.c:172:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(request->bytes, hdr_bytes, RTRPDU_HDR_LEN); data/fort-validator-1.4.2/src/rtr/pdu.c:223:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:232:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:241:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:250:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:259:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:273:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:287:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:296:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:305:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.c:316:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&pdu->header, header, sizeof(*header)); data/fort-validator-1.4.2/src/rtr/pdu.h:126:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char ski[RK_SKI_LEN]; data/fort-validator-1.4.2/src/rtr/pdu.h:129:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char spki[RK_SPKI_LEN]; data/fort-validator-1.4.2/src/rtr/pdu.h:136:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char erroneous_pdu[RTRPDU_ERR_MAX_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:48:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_SERIAL_NOTIFY_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:68:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_CACHE_RESET_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:86:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_CACHE_RESPONSE_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:104:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET_ADDRSTRLEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:115:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_IPV4_PREFIX_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:140:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:151:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_IPV6_PREFIX_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:191:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[RTRPDU_ROUTER_KEY_LEN]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:205:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(pdu.ski, router_key->ski, RK_SKI_LEN); data/fort-validator-1.4.2/src/rtr/pdu_sender.c:208:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(pdu.spki, router_key->spk, RK_SPKI_LEN); data/fort-validator-1.4.2/src/rtr/pdu_sender.c:273:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char data[GET_END_OF_DATA_LENGTH(version)]; data/fort-validator-1.4.2/src/rtr/pdu_sender.c:315:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(pdu.erroneous_pdu, request->bytes, pdu.error_pdu_length); data/fort-validator-1.4.2/src/rtr/pdu_serializer.c:152:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(ptr, pdu->erroneous_pdu, pdu->error_pdu_length); data/fort-validator-1.4.2/src/rtr/pdu_serializer.c:158:3: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(ptr, pdu->error_message, pdu->error_message_length); data/fort-validator-1.4.2/src/rtr/primitive_reader.c:232:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(string, reader->buffer, string_len); data/fort-validator-1.4.2/src/rtr/primitive_reader.c:248:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(result, reader->buffer, num); data/fort-validator-1.4.2/src/rtr/rtr.c:266:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp_addr, full_address, tmp_addr_len); data/fort-validator-1.4.2/src/rtr/rtr.c:385:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/rtr/rtr.c:405:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char buffer[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/slurm/db_slurm.c:42:8: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char addr_buf[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/slurm/db_slurm.c:400:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, key->ski, RK_SKI_LEN); data/fort-validator-1.4.2/src/slurm/db_slurm.h:35:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char csum[EVP_MAX_MD_SIZE]; data/fort-validator-1.4.2/src/sorted_array.c:122:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(get_nth_element(sarray, sarray->count), element, sarray->size); data/fort-validator-1.4.2/src/state.c:44:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char addr_buffer1[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/state.c:45:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char addr_buffer2[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/src/str_token.c:19:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(result, string, size); data/fort-validator-1.4.2/src/xml/relax_ng.c:17:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char log_msg[LOG_MSG_LEN]; \ data/fort-validator-1.4.2/test/http_test.c:36:2: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(&resp->content[resp->size], content, read); data/fort-validator-1.4.2/test/impersonator.c:10:8: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char addr_buffer1[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/test/impersonator.c:11:8: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. static char addr_buffer2[INET6_ADDRSTRLEN]; data/fort-validator-1.4.2/test/rtr/pdu_handler_test.c:429:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char buf[BUF_SIZE]; data/fort-validator-1.4.2/test/rtr/pdu_test.c:20:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char read[sizeof(buffer)]; \ data/fort-validator-1.4.2/test/rtr/pdu_test.c:125:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char read[RTRPDU_HDR_LEN]; data/fort-validator-1.4.2/test/rtr/pdu_test.c:257:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char sub_pdu_read[12]; data/fort-validator-1.4.2/test/rtr/pdu_test.c:303:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char read[4]; data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c:20:11: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. unsigned char read_bytes[size]; data/fort-validator-1.4.2/test/xml_test.c:44:4: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(tmp, tmp_char, xmlStrlen(tmp_char)); data/fort-validator-1.4.2/src/asn1/asn1c/GeneralizedTime.c:125:18: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t tzlen = strlen(tzold); \ data/fort-validator-1.4.2/src/asn1/asn1c/OBJECT_IDENTIFIER.c:479:20: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). oid_txt_length = strlen(oid_text); data/fort-validator-1.4.2/src/asn1/asn1c/OCTET_STRING.c:1782:9: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). len = strlen(str); data/fort-validator-1.4.2/src/asn1/asn1c/constr_CHOICE.c:802:23: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). unsigned int mlen = strlen(mname); data/fort-validator-1.4.2/src/asn1/asn1c/constr_CHOICE.c:1043:21: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if(cb(elm->name, strlen(elm->name), app_key) < 0 data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:886:29: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). unsigned int mlen = strlen(mname); data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:944:18: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if(cb(td->name, strlen(td->name), app_key) < 0 data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE.c:967:20: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if(cb(elm->name, strlen(elm->name), app_key) < 0 data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE_OF.c:101:27: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t mlen = mname ? strlen(mname) : 0; data/fort-validator-1.4.2/src/asn1/asn1c/constr_SEQUENCE_OF.c:125:26: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t len = strlen(name); data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:706:24: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t mlen = mname ? strlen(mname) : 0; data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:750:17: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t len = strlen(name); data/fort-validator-1.4.2/src/asn1/asn1c/constr_SET_OF.c:806:18: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if(cb(td->name, strlen(td->name), app_key) < 0 data/fort-validator-1.4.2/src/asn1/asn1c/xer_encoder.c:25:9: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). mlen = strlen(mname); data/fort-validator-1.4.2/src/asn1/signed_data.c:492:7: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. bool equal; data/fort-validator-1.4.2/src/asn1/signed_data.c:514:7: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (equal) { data/fort-validator-1.4.2/src/common.c:113:21: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp = realloc(tmp, strlen(tmp) + 1 + strlen(file_name) + 1); data/fort-validator-1.4.2/src/common.c:113:39: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp = realloc(tmp, strlen(tmp) + 1 + strlen(file_name) + 1); data/fort-validator-1.4.2/src/common.c:117:2: [1] (buffer) strcat: Does not check for buffer overflows when concatenating to destination [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or snprintf (warning: strncat is easily misused). Risk is low because the source is a constant character. strcat(tmp, "/"); data/fort-validator-1.4.2/src/common.c:372:15: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). config_len = strlen(config_repo); data/fort-validator-1.4.2/src/common.c:388:7: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if (strlen(work_loc) == config_len) data/fort-validator-1.4.2/src/common.c:447:19: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). repository_len = strlen(repository); data/fort-validator-1.4.2/src/common.c:448:19: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). uri_prefix_len = strlen(uri_prefix); data/fort-validator-1.4.2/src/common.c:449:12: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). uri_len = strlen(uri); data/fort-validator-1.4.2/src/common.c:457:19: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). workspace_len = strlen(workspace); data/fort-validator-1.4.2/src/common.c:468:3: [1] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant character. strcpy(local + offset, "/"); data/fort-validator-1.4.2/src/common.c:475:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(local + offset, uri, uri_len); data/fort-validator-1.4.2/src/config/boolean.c:19:21: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if (str == NULL || strlen(str) == 0) { data/fort-validator-1.4.2/src/config/str.c:28:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(str) == 0) { data/fort-validator-1.4.2/src/config/string_array.c:148:41: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). string_tokenizer_init(&tokenizer, str, strlen(str), ','); data/fort-validator-1.4.2/src/config/uint.c:23:7: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(str) == 0) { data/fort-validator-1.4.2/src/crypto/base64.c:148:16: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). encoded_len = strlen(str_encoded); data/fort-validator-1.4.2/src/crypto/base64.c:173:33: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). alloc_size = EVP_DECODE_LENGTH(strlen(str_copy)); data/fort-validator-1.4.2/src/crypto/hash.c:253:15: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). src = malloc(strlen(str)); data/fort-validator-1.4.2/src/crypto/hash.c:257:19: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). memcpy(src, str, strlen(str)); data/fort-validator-1.4.2/src/crypto/hash.c:259:38: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). error = hash_buffer(algorithm, src, strlen(str), result, result_len); data/fort-validator-1.4.2/src/data_structure/uthash.h:92:26: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). #define uthash_strlen(s) strlen(s) data/fort-validator-1.4.2/src/delete_dir_daemon.c:145:13: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp_size = strlen(local_path); data/fort-validator-1.4.2/src/delete_dir_daemon.c:146:47: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if (strrchr(local_path, '/') == local_path + strlen(local_path) - 1) data/fort-validator-1.4.2/src/delete_dir_daemon.c:154:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(tmp, local_path, tmp_size); data/fort-validator-1.4.2/src/delete_dir_daemon.c:180:14: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). rcvd_size = strlen(rcvd); data/fort-validator-1.4.2/src/http/http.c:107:9: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). return strlen(handler->errbuf) > 0 ? data/fort-validator-1.4.2/src/http/http.c:192:26: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp = realloc(tmp_file, strlen(tmp_file) + strlen(tmp_suffix) + 1); data/fort-validator-1.4.2/src/http/http.c:192:45: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp = realloc(tmp_file, strlen(tmp_file) + strlen(tmp_suffix) + 1); data/fort-validator-1.4.2/src/object/certificate.c:247:43: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). error = uri_create_rsync_str(&uri, file, strlen(file)); data/fort-validator-1.4.2/src/object/certificate.c:1181:22: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t prefix_len = strlen(PREFIX); data/fort-validator-1.4.2/src/object/certificate.c:1184:45: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ? (strncmp((char *) uri->data, PREFIX, strlen(PREFIX)) == 0) data/fort-validator-1.4.2/src/object/certificate.c:2337:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(tmp, global, i); data/fort-validator-1.4.2/src/object/tal.c:105:42: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). error = uri_create_mixed_str(&new, uri, strlen(uri)); data/fort-validator-1.4.2/src/object/tal.c:507:9: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). return read; data/fort-validator-1.4.2/src/object/vcard.c:176:24: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t expected_len = strlen(expected); data/fort-validator-1.4.2/src/object/vcard.c:204:50: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). return strncasecmp((char *) line->str.val, tag, strlen(tag)) == 0; data/fort-validator-1.4.2/src/reqs_errors.c:176:49: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). HASH_ADD_KEYPTR(hh, err_uris_db, new_uri->uri, strlen(new_uri->uri), data/fort-validator-1.4.2/src/reqs_errors.c:299:17: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). *(str_time + strlen(str_time) - 1) = ' '; data/fort-validator-1.4.2/src/rrdp/db/db_rrdp_uris.c:102:49: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). HASH_ADD_KEYPTR(hh, uris->table, new_uri->uri, strlen(new_uri->uri), data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:109:9: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). return read; data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:144:13: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp_size = strlen(from); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:244:33: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). alloc_size = EVP_DECODE_LENGTH(strlen(content)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:527:7: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(tmp->doc_data.uri)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:569:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(tmp->doc_data.uri)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:599:52: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). error = uri_create_rsync_str_rrdp(&uri, location, strlen(location)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:658:52: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). error = uri_create_rsync_str_rrdp(&uri, location, strlen(location)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:1036:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(head_data->uri)); data/fort-validator-1.4.2/src/rrdp/rrdp_parser.c:1131:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(parent->snapshot.uri)); data/fort-validator-1.4.2/src/rsync/rsync.c:279:40: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). log_buffer(char const *buffer, ssize_t read, int type, bool log_operation) data/fort-validator-1.4.2/src/rsync/rsync.c:289:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(cpy, buffer, read); data/fort-validator-1.4.2/src/rsync/rsync.c:289:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). strncpy(cpy, buffer, read); data/fort-validator-1.4.2/src/rsync/rsync.c:290:6: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). cpy[read] = '\0'; data/fort-validator-1.4.2/src/rsync/rsync.c:296:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if(strlen(cur) == 0) { data/fort-validator-1.4.2/src/rsync/rsync.c:320:11: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). count = read(fd_pipe[type][0], buffer, sizeof(buffer)); data/fort-validator-1.4.2/src/rsync/rsync.c:513:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(error_uri)); data/fort-validator-1.4.2/src/rtr/pdu_sender.c:320:49: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). pdu.error_message_length = (message != NULL) ? strlen(message) : 0; data/fort-validator-1.4.2/src/rtr/primitive_reader.c:34:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). read_result = read(fd, &buffer[offset], buffer_len - offset); data/fort-validator-1.4.2/src/rtr/rtr.c:261:17: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp_addr_len = strlen(full_address) - strlen(ptr); data/fort-validator-1.4.2/src/rtr/rtr.c:261:40: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). tmp_addr_len = strlen(full_address) - strlen(ptr); data/fort-validator-1.4.2/src/slurm/db_slurm.c:133:7: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. bool equal; data/fort-validator-1.4.2/src/slurm/db_slurm.c:166:6: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (equal && (filter->data_flag & SLURM_COM_FLAG_ASN) > 0) data/fort-validator-1.4.2/src/slurm/db_slurm.c:169:6: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (equal && (filter->data_flag & SLURM_PFX_FLAG_PREFIX) > 0) data/fort-validator-1.4.2/src/slurm/db_slurm.c:172:9: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. return equal; data/fort-validator-1.4.2/src/slurm/db_slurm.c:193:7: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. bool equal; data/fort-validator-1.4.2/src/slurm/db_slurm.c:222:6: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (equal && (filter->data_flag & SLURM_COM_FLAG_ASN) > 0) data/fort-validator-1.4.2/src/slurm/db_slurm.c:225:6: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (equal && (filter->data_flag & SLURM_BGPS_FLAG_SKI) > 0) data/fort-validator-1.4.2/src/slurm/db_slurm.c:228:9: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. return equal; data/fort-validator-1.4.2/src/uri.c:132:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(uri->global, str, str_len); data/fort-validator-1.4.2/src/uri.c:175:3: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(joined, (char *) ia5->buf, ia5->size); data/fort-validator-1.4.2/src/uri.c:186:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(joined, mft, dir_len); data/fort-validator-1.4.2/src/uri.c:187:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(joined + dir_len, (char *) ia5->buf, ia5->size); data/fort-validator-1.4.2/src/uri.c:216:31: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t const PFX_RSYNC_LEN = strlen(PFX_RSYNC); data/fort-validator-1.4.2/src/uri.c:217:31: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). size_t const PFX_HTTPS_LEN = strlen(PFX_HTTPS); data/fort-validator-1.4.2/src/uri.c:529:12: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ext_len = strlen(ext); data/fort-validator-1.4.2/src/visited_uris.c:117:46: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). HASH_ADD_KEYPTR(hh, uris->table, elem->uri, strlen(elem->uri), data/fort-validator-1.4.2/src/visited_uris.c:151:3: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(tmp, elem->uri, size); data/fort-validator-1.4.2/src/xml/relax_ng.c:45:10: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if (ptr[strlen(ptr) - 1] == '\n') data/fort-validator-1.4.2/src/xml/relax_ng.c:46:7: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ptr[strlen(ptr) - 1] = '\0'; data/fort-validator-1.4.2/src/xml/relax_ng.c:90:6: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). int read; data/fort-validator-1.4.2/src/xml/relax_ng.c:132:6: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (read < 0) { data/fort-validator-1.4.2/src/xml/relax_ng.h:163:26: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). #define RRDP_V1_RNG_SIZE strlen(RRDP_V1_RNG) data/fort-validator-1.4.2/test/http_test.c:36:46: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). memcpy(&resp->content[resp->size], content, read); data/fort-validator-1.4.2/test/http_test.c:37:16: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). resp->size += read; data/fort-validator-1.4.2/test/http_test.c:40:9: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). return read; data/fort-validator-1.4.2/test/line_file_test.c:37:17: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). SENTENCE_LEN = strlen(SENTENCE); data/fort-validator-1.4.2/test/rsync_test.c:32:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(ancestor))); data/fort-validator-1.4.2/test/rsync_test.c:34:6: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). strlen(descendant))); data/fort-validator-1.4.2/test/rsync_test.c:66:58: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ck_assert_int_eq(0, uri_create_rsync_str(&uri, uri_str, strlen(uri_str))); data/fort-validator-1.4.2/test/rsync_test.c:75:58: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ck_assert_int_eq(0, uri_create_rsync_str(&uri, uri_str, strlen(uri_str))); data/fort-validator-1.4.2/test/rsync_test.c:116:55: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). ck_assert_int_eq(0, uri_create_rsync_str(&src, test, strlen(test))); data/fort-validator-1.4.2/test/rtr/pdu_test.c:20:16: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). unsigned char read[sizeof(buffer)]; \ data/fort-validator-1.4.2/test/rtr/pdu_test.c:25:48: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ck_assert_int_eq(pdu_reader_init(&reader, fd, read, \ data/fort-validator-1.4.2/test/rtr/pdu_test.c:125:16: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). unsigned char read[RTRPDU_HDR_LEN]; data/fort-validator-1.4.2/test/rtr/pdu_test.c:133:48: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ck_assert_int_eq(pdu_reader_init(&reader, fd, read, RTRPDU_HDR_LEN, data/fort-validator-1.4.2/test/rtr/pdu_test.c:303:16: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). unsigned char read[4]; data/fort-validator-1.4.2/test/rtr/pdu_test.c:308:37: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). err = pdu_reader_init(&reader, fd, read, 4, true); data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c:130:16: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). pattern_len = strlen(pattern); data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c:155:15: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). actual_len = strlen(str); data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c:163:16: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). pattern_len = strlen(pattern); data/fort-validator-1.4.2/test/rtr/primitive_reader_test.c:172:31: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). if (strncmp(pattern, cursor, strlen(cursor)) != 0) { data/fort-validator-1.4.2/test/vcard_test.c:19:14: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). str8.size = strlen(str); \ data/fort-validator-1.4.2/test/vcard_test.c:84:15: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). str8.size += strlen(" ame\r\n" VC_ORG VC_END); data/fort-validator-1.4.2/test/vcard_test.c:91:15: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). str8.size += strlen(" 0\r\n" VC_FN VC_ORG VC_END); ANALYSIS SUMMARY: Hits = 313 Lines analyzed = 62380 in approximately 1.44 seconds (43376 lines/second) Physical Source Lines of Code (SLOC) = 45078 Hits@level = [0] 65 [1] 119 [2] 164 [3] 6 [4] 24 [5] 0 Hits@level+ = [0+] 378 [1+] 313 [2+] 194 [3+] 30 [4+] 24 [5+] 0 Hits/KSLOC@level+ = [0+] 8.38547 [1+] 6.94352 [2+] 4.30365 [3+] 0.665513 [4+] 0.53241 [5+] 0 Dot directories skipped = 1 (--followdotdir overrides) Minimum risk level = 1 Not every hit is necessarily a security vulnerability. There may be other security vulnerabilities; review your code! See 'Secure Programming HOWTO' (https://dwheeler.com/secure-programs) for more information.