Searching saned software vulnerabilities

saned in sane-backends 1.0.7 and earlier does n

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier does not check the IP address of the connecting host during the SANE_NET_INIT RPC call, which allows remote attackers to use that call even if they are restricted in saned.conf.


saned in sane-backends 1.0.7 and earlier does n

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier does not quickly handle connection drops, which allows remote attackers to cause a denial of service (segmentation fault) when invalid memory is accessed.


saned in sane-backends 1.0.7 and earlier calls

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier calls malloc with an arbitrary size value if a connection is dropped before the size value has been sent, which allows remote attackers to cause a denial of service (memory consumption or crash).


saned in sane-backends 1.0.7 and earlier does n

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier does not properly "check the validity of the RPC numbers it gets before getting the parameters," with unknown consequences.


saned in sane-backends 1.0.7 and earlier, when

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier, when debug messages are enabled, does not properly handle dropped connections, which can prevent strings from being null terminated and cause a denial of service (segmentation fault).


saned in sane-backends 1.0.7 and earlier, and p

sane-backends | saned |

saned in sane-backends 1.0.7 and earlier, and possibly later versions, does not properly allocate memory in certain cases, which could allow attackers to cause a denial of service (memory consumption).


Software vulnerabilities results 1 to 7 of 7     
Page: 1