• Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings
Vulnerability in Scanner Access Now Easy (SANE) before 1.0.5, related to pnm and saned.
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
Date Entry Created
20020607 Disclaimer: The entry creation date may reflect when the CVE-ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Proposed (20020611)
Votes (Legacy)
ACCEPT(3) Alderson, Cole, Green
MODIFY(2) Cox, Frech
NOOP(2) Foat, Wall
Comments (Legacy)
 CHANGE> [Cox changed vote from REVIEWING to MODIFY]
 Cox> I'm not sure how to vote on this, I did the research and read
   the changlog and it appears that the issue you mention here has not
   been fixed at all; merely documented as of sane version 1.0.5
   Change description based on the information in the Sane tarball; note that 
   this affects all versions to date and is not fixed.
   - Security problems with pnm
   If the pnm backend is installed and saned is used to allow users on
   remote computers to scan on the local machine, pnm files can be read by
   the remote user. This is limited to the files saned can access (usually
   it's running as user "sane"). All pnm files can be read if saned runs
   as root which isn't recommended anyway. The pnm backend is disabled
   by default. If you want to use it, enable it with configure (see 
   configure --help for details). Be sure that only trusted users can
   access the pnm backend over saned.
 Frech> XF:sane-prm-read-files(9853)

Proposed (Legacy)
This is an entry on the CVE list, which standardizes names for security problems.