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/yapet-2.5/intl.h
Examining data/yapet-2.5/gettext.h
Examining data/yapet-2.5/libyacurs/include/sigaction.h
Examining data/yapet-2.5/libyacurs/include/libyacurscfg.h
Examining data/yapet-2.5/libyacurs/include/coordinates.h
Examining data/yapet-2.5/libyacurs/include/yacursex.h
Examining data/yapet-2.5/libyacurs/include/curstr.h
Examining data/yapet-2.5/libyacurs/include/curswin.h
Examining data/yapet-2.5/libyacurs/include/cursorbuf.h
Examining data/yapet-2.5/libyacurs/include/curs.h
Examining data/yapet-2.5/libyacurs/include/eventconnector.h
Examining data/yapet-2.5/libyacurs/include/event.h
Examining data/yapet-2.5/libyacurs/include/eventqueue.h
Examining data/yapet-2.5/libyacurs/include/lineobject.h
Examining data/yapet-2.5/libyacurs/include/margin.h
Examining data/yapet-2.5/libyacurs/include/yacurscurses.h
Examining data/yapet-2.5/libyacurs/include/pack.h
Examining data/yapet-2.5/libyacurs/include/realizeable.h
Examining data/yapet-2.5/libyacurs/include/area.h
Examining data/yapet-2.5/libyacurs/include/windowbase.h
Examining data/yapet-2.5/libyacurs/include/titlebar.h
Examining data/yapet-2.5/libyacurs/include/statusbar.h
Examining data/yapet-2.5/libyacurs/include/vpack.h
Examining data/yapet-2.5/libyacurs/include/widgetbase.h
Examining data/yapet-2.5/libyacurs/include/hotkey.h
Examining data/yapet-2.5/libyacurs/include/window.h
Examining data/yapet-2.5/libyacurs/include/lockscreen.h
Examining data/yapet-2.5/libyacurs/include/yacurs.h
Examining data/yapet-2.5/libyacurs/include/hpack.h
Examining data/yapet-2.5/libyacurs/include/label.h
Examining data/yapet-2.5/libyacurs/include/dynlabel.h
Examining data/yapet-2.5/libyacurs/include/size.h
Examining data/yapet-2.5/libyacurs/include/widget.h
Examining data/yapet-2.5/libyacurs/include/focusgroup.h
Examining data/yapet-2.5/libyacurs/include/focusmanager.h
Examining data/yapet-2.5/libyacurs/include/button.h
Examining data/yapet-2.5/libyacurs/include/colors.h
Examining data/yapet-2.5/libyacurs/include/colorparser.h
Examining data/yapet-2.5/libyacurs/include/input.h
Examining data/yapet-2.5/libyacurs/include/listbox.h
Examining data/yapet-2.5/libyacurs/include/yacursconst.h
Examining data/yapet-2.5/libyacurs/include/yacurstypes.h
Examining data/yapet-2.5/libyacurs/include/dialog.h
Examining data/yapet-2.5/libyacurs/include/messagebox.h
Examining data/yapet-2.5/libyacurs/include/messagebox2.h
Examining data/yapet-2.5/libyacurs/include/messagebox3.h
Examining data/yapet-2.5/libyacurs/include/inputbox.h
Examining data/yapet-2.5/libyacurs/include/filedialog.h
Examining data/yapet-2.5/libyacurs/include/filesavedialog.h
Examining data/yapet-2.5/libyacurs/include/fileloaddialog.h
Examining data/yapet-2.5/libyacurs/include/checkbox.h
Examining data/yapet-2.5/libyacurs/include/radiobox.h
Examining data/yapet-2.5/libyacurs/include/unlockdialog.h
Examining data/yapet-2.5/libyacurs/include/unlockdiadefault.h
Examining data/yapet-2.5/libyacurs/include/evtqueuestats.h
Examining data/yapet-2.5/libyacurs/include/rule.h
Examining data/yapet-2.5/libyacurs/include/vrule.h
Examining data/yapet-2.5/libyacurs/include/hrule.h
Examining data/yapet-2.5/libyacurs/include/spacer.h
Examining data/yapet-2.5/libyacurs/include/yacursdbg.h
Examining data/yapet-2.5/libyacurs/include/gettext.h
Examining data/yapet-2.5/libyacurs/src/sigaction.cc
Examining data/yapet-2.5/libyacurs/src/coordinates.cc
Examining data/yapet-2.5/libyacurs/src/size.cc
Examining data/yapet-2.5/libyacurs/src/margin.cc
Examining data/yapet-2.5/libyacurs/src/area.cc
Examining data/yapet-2.5/libyacurs/src/curstr.cc
Examining data/yapet-2.5/libyacurs/src/curswin.cc
Examining data/yapet-2.5/libyacurs/src/cursorbuf.cc
Examining data/yapet-2.5/libyacurs/src/event.cc
Examining data/yapet-2.5/libyacurs/src/eventconnector.cc
Examining data/yapet-2.5/libyacurs/src/eventqueue.cc
Examining data/yapet-2.5/libyacurs/src/evtqueuestats.cc
Examining data/yapet-2.5/libyacurs/src/curs.cc
Examining data/yapet-2.5/libyacurs/src/realizeable.cc
Examining data/yapet-2.5/libyacurs/src/titlebar.cc
Examining data/yapet-2.5/libyacurs/src/statusbar.cc
Examining data/yapet-2.5/libyacurs/src/windowbase.cc
Examining data/yapet-2.5/libyacurs/src/hotkey.cc
Examining data/yapet-2.5/libyacurs/src/window.cc
Examining data/yapet-2.5/libyacurs/src/lockscreen.cc
Examining data/yapet-2.5/libyacurs/src/lineobject.cc
Examining data/yapet-2.5/libyacurs/src/widgetbase.cc
Examining data/yapet-2.5/libyacurs/src/pack.cc
Examining data/yapet-2.5/libyacurs/src/vpack.cc
Examining data/yapet-2.5/libyacurs/src/hpack.cc
Examining data/yapet-2.5/libyacurs/src/widget.cc
Examining data/yapet-2.5/libyacurs/src/label.cc
Examining data/yapet-2.5/libyacurs/src/dynlabel.cc
Examining data/yapet-2.5/libyacurs/src/yacursex.cc
Examining data/yapet-2.5/libyacurs/src/colors.cc
Examining data/yapet-2.5/libyacurs/src/colorparser.cc
Examining data/yapet-2.5/libyacurs/src/focusgroup.cc
Examining data/yapet-2.5/libyacurs/src/focusmanager.cc
Examining data/yapet-2.5/libyacurs/src/button.cc
Examining data/yapet-2.5/libyacurs/src/dialog.cc
Examining data/yapet-2.5/libyacurs/src/messagebox.cc
Examining data/yapet-2.5/libyacurs/src/messagebox2.cc
Examining data/yapet-2.5/libyacurs/src/messagebox3.cc
Examining data/yapet-2.5/libyacurs/src/inputbox.cc
Examining data/yapet-2.5/libyacurs/src/filedialog.cc
Examining data/yapet-2.5/libyacurs/src/filesavedialog.cc
Examining data/yapet-2.5/libyacurs/src/fileloaddialog.cc
Examining data/yapet-2.5/libyacurs/src/checkbox.cc
Examining data/yapet-2.5/libyacurs/src/radiobox.cc
Examining data/yapet-2.5/libyacurs/src/unlockdialog.cc
Examining data/yapet-2.5/libyacurs/src/unlockdiadefault.cc
Examining data/yapet-2.5/libyacurs/src/rule.cc
Examining data/yapet-2.5/libyacurs/src/hrule.cc
Examining data/yapet-2.5/libyacurs/src/vrule.cc
Examining data/yapet-2.5/libyacurs/src/spacer.cc
Examining data/yapet-2.5/libyacurs/src/yacursdbg.cc
Examining data/yapet-2.5/libyacurs/tests/preloadlib/testpreload.cc
Examining data/yapet-2.5/libyacurs/tests/basic/area.cc
Examining data/yapet-2.5/libyacurs/tests/basic/colorparser.cc
Examining data/yapet-2.5/libyacurs/tests/basic/coordinates.cc
Examining data/yapet-2.5/libyacurs/tests/basic/cursorbuf1.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventconnector1.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue1.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue2.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue3.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue4.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue5.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue6.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue7.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue8.cc
Examining data/yapet-2.5/libyacurs/tests/basic/eventqueue9.cc
Examining data/yapet-2.5/libyacurs/tests/basic/margin.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/app1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/checkbox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/dialog1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog3.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/focus1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/input1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/inputbox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/listbox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/listbox2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/lockscreen1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox3.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/packremove.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/radiobox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/resize3.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/resize4.cc
Examining data/yapet-2.5/libyacurs/tests/ui-interactive/resize5.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/basic1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/basic2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursinit.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin3.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/dynlabel1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/dynlabel2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/hrule1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/listbox1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack3.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack4.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack5.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack6.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack7.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack8.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/pack9.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/packresize1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/resize1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/resize2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/vrule1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/widget1.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/widget2.cc
Examining data/yapet-2.5/libyacurs/tests/ui-non-interactive/widget3.cc
Examining data/yapet-2.5/src/libs/logger.cc
Examining data/yapet-2.5/src/libs/consts/consts.cc
Examining data/yapet-2.5/src/libs/consts/consts.h
Examining data/yapet-2.5/src/libs/cfg/cfg.cc
Examining data/yapet-2.5/src/libs/cfg/cfg.h
Examining data/yapet-2.5/src/libs/cfg/cfgfile.cc
Examining data/yapet-2.5/src/libs/cfg/cfgfile.h
Examining data/yapet-2.5/src/libs/globals/globals.cc
Examining data/yapet-2.5/src/libs/globals/globals.h
Examining data/yapet-2.5/src/libs/utils/securearray.cc
Examining data/yapet-2.5/src/libs/metadata/metadata.cc
Examining data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc
Examining data/yapet-2.5/src/libs/passwordrecord/passwordlistitem.cc
Examining data/yapet-2.5/src/libs/file/rawfile.cc
Examining data/yapet-2.5/src/libs/file/fileutils.cc
Examining data/yapet-2.5/src/libs/file/yapetfile.cc
Examining data/yapet-2.5/src/libs/file/yapet10file.cc
Examining data/yapet-2.5/src/libs/file/yapet20file.cc
Examining data/yapet-2.5/src/libs/file/header10.cc
Examining data/yapet-2.5/src/libs/file/filehelper.cc
Examining data/yapet-2.5/src/libs/crypt/file.h
Examining data/yapet-2.5/src/libs/crypt/key448.cc
Examining data/yapet-2.5/src/libs/crypt/key256.cc
Examining data/yapet-2.5/src/libs/crypt/file.cc
Examining data/yapet-2.5/src/libs/crypt/blowfish.cc
Examining data/yapet-2.5/src/libs/crypt/aes256.cc
Examining data/yapet-2.5/src/libs/crypt/crypto.cc
Examining data/yapet-2.5/src/libs/crypt/blowfishfactory.cc
Examining data/yapet-2.5/src/libs/crypt/aes256factory.cc
Examining data/yapet-2.5/src/libs/crypt/cryptofactoryhelper.cc
Examining data/yapet-2.5/src/libs/glue/loadfile.cc
Examining data/yapet-2.5/src/libs/glue/promptpassword.cc
Examining data/yapet-2.5/src/libs/glue/createfile.cc
Examining data/yapet-2.5/src/libs/glue/changepassword.cc
Examining data/yapet-2.5/src/libs/glue/loadfile.h
Examining data/yapet-2.5/src/libs/glue/promptpassword.h
Examining data/yapet-2.5/src/libs/glue/createfile.h
Examining data/yapet-2.5/src/libs/glue/changepassword.h
Examining data/yapet-2.5/src/libs/glue/opencmdlinefile.cc
Examining data/yapet-2.5/src/libs/glue/opencmdlinefile.h
Examining data/yapet-2.5/src/libs/pwgen/rngengine.cc
Examining data/yapet-2.5/src/libs/pwgen/rng.cc
Examining data/yapet-2.5/src/libs/pwgen/pwgen.cc
Examining data/yapet-2.5/src/libs/pwgen/characterpool.cc
Examining data/yapet-2.5/src/libs/ui/help.cc
Examining data/yapet-2.5/src/libs/ui/mainwindow.cc
Examining data/yapet-2.5/src/libs/ui/passworddialog.cc
Examining data/yapet-2.5/src/libs/ui/passwordrecord.cc
Examining data/yapet-2.5/src/libs/ui/newpassworddialog.cc
Examining data/yapet-2.5/src/libs/ui/info.cc
Examining data/yapet-2.5/src/libs/ui/yapetunlockdialog.cc
Examining data/yapet-2.5/src/libs/ui/yapetlockscreen.cc
Examining data/yapet-2.5/src/libs/ui/help.h
Examining data/yapet-2.5/src/libs/ui/mainwindow.h
Examining data/yapet-2.5/src/libs/ui/passworddialog.h
Examining data/yapet-2.5/src/libs/ui/passwordrecord.h
Examining data/yapet-2.5/src/libs/ui/newpassworddialog.h
Examining data/yapet-2.5/src/libs/ui/info.h
Examining data/yapet-2.5/src/libs/ui/yapetunlockdialog.h
Examining data/yapet-2.5/src/libs/ui/yapetlockscreen.h
Examining data/yapet-2.5/src/libs/ui/pwgendialog.h
Examining data/yapet-2.5/src/libs/ui/pwgendialog.cc
Examining data/yapet-2.5/src/libs/ui/mainwindowhotkeys.h
Examining data/yapet-2.5/src/yapet/main.cc
Examining data/yapet-2.5/src/converters/csv/csvstringfield.cc
Examining data/yapet-2.5/src/converters/csv/csvline.cc
Examining data/yapet-2.5/src/converters/csv2yapet/csvimport.h
Examining data/yapet-2.5/src/converters/csv2yapet/csvimport.cc
Examining data/yapet-2.5/src/converters/csv2yapet/main.cc
Examining data/yapet-2.5/src/converters/yapet2csv/csvexport.h
Examining data/yapet-2.5/src/converters/yapet2csv/csvexport.cc
Examining data/yapet-2.5/src/converters/yapet2csv/main.cc
Examining data/yapet-2.5/tests/utils/ods.cc
Examining data/yapet-2.5/tests/utils/securearray.cc
Examining data/yapet-2.5/tests/utils/utils.cc
Examining data/yapet-2.5/tests/metadata/metadata.cc
Examining data/yapet-2.5/tests/passwordrecord/passwordlistitem.cc
Examining data/yapet-2.5/tests/passwordrecord/passwordrecord.cc
Examining data/yapet-2.5/tests/crypt/aes256.cc
Examining data/yapet-2.5/tests/crypt/aes256factory.cc
Examining data/yapet-2.5/tests/crypt/blowfish.cc
Examining data/yapet-2.5/tests/crypt/blowfishfactory.cc
Examining data/yapet-2.5/tests/crypt/cryptofactoryhelper.cc
Examining data/yapet-2.5/tests/crypt/file_aes256.cc
Examining data/yapet-2.5/tests/crypt/file_blowfish.cc
Examining data/yapet-2.5/tests/crypt/foreign.cc
Examining data/yapet-2.5/tests/crypt/key256.cc
Examining data/yapet-2.5/tests/crypt/key448.cc
Examining data/yapet-2.5/tests/crypt/passwordchange_exerciser.cc
Examining data/yapet-2.5/tests/cfg/cfg1.cc
Examining data/yapet-2.5/tests/cfg/cfgfile1.cc
Examining data/yapet-2.5/tests/file/filehelper.cc
Examining data/yapet-2.5/tests/file/fileutils.cc
Examining data/yapet-2.5/tests/file/header10.cc
Examining data/yapet-2.5/tests/file/headerversion.cc
Examining data/yapet-2.5/tests/file/rawfile.cc
Examining data/yapet-2.5/tests/file/yapet10file.cc
Examining data/yapet-2.5/tests/file/yapet20file.cc
Examining data/yapet-2.5/tests/file/yapetfile.cc
Examining data/yapet-2.5/tests/pwgen/characterpool.cc
Examining data/yapet-2.5/tests/pwgen/pwgen.cc
Examining data/yapet-2.5/tests/pwgen/pwgen_distribution.cc
Examining data/yapet-2.5/tests/pwgen/rng.cc
Examining data/yapet-2.5/tests/pwgen/rng_distribution.cc
Examining data/yapet-2.5/tests/pwgen/rng_engine.cc
Examining data/yapet-2.5/tests/converters/csv/csvline.cc
Examining data/yapet-2.5/tests/converters/csv/csvstringfield.cc
Examining data/yapet-2.5/tests/converters/import/import.cc
Examining data/yapet-2.5/tests/converters/import/import2.cc
Examining data/yapet-2.5/tests/preload/checkmasterpwchange.cc
Examining data/yapet-2.5/tests/preload/checktestpwrecord.cc
Examining data/yapet-2.5/tests/preload/istty.cc
Examining data/yapet-2.5/tests/preload/pwrecord.cc
Examining data/yapet-2.5/tests/preload/checkyapet.cc
Examining data/yapet-2.5/tests/preload/masterpwchange.cc
FINAL RESULTS:
data/yapet-2.5/src/libs/file/fileutils.cc:67:20: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
auto error = ::chown(filename.c_str(), uid, gid);
data/yapet-2.5/src/libs/file/fileutils.cc:75:15: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
error = ::chmod(filename.c_str(), S_IRUSR | S_IWUSR);
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:115:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access(srcfile.c_str(), R_OK | F_OK) == -1) {
data/yapet-2.5/src/converters/csv2yapet/main.cc:242:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access(dstfile.c_str(), F_OK) == 0) {
data/yapet-2.5/src/converters/yapet2csv/csvexport.cc:68:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access(srcfile.c_str(), R_OK | F_OK) == -1) {
data/yapet-2.5/src/converters/yapet2csv/main.cc:243:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access(dstfile.c_str(), F_OK) == 0) {
data/yapet-2.5/src/libs/cfg/cfgfile.cc:55:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access(filepath.c_str(), R_OK | F_OK) == -1) {
data/yapet-2.5/src/libs/glue/opencmdlinefile.cc:180:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (::access(_file.c_str(), F_OK | R_OK) == -1) {
data/yapet-2.5/tests/converters/import/import.cc:256:14: [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.
std::snprintf(name, yapet::PasswordRecord::NAME_SIZE, NAME_FORMAT,
data/yapet-2.5/tests/converters/import/import.cc:258:14: [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.
std::snprintf(host, yapet::PasswordRecord::HOST_SIZE, HOST_FORMAT,
data/yapet-2.5/tests/converters/import/import.cc:260:14: [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.
std::snprintf(username, yapet::PasswordRecord::USERNAME_SIZE,
data/yapet-2.5/tests/converters/import/import.cc:262:14: [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.
std::snprintf(password, yapet::PasswordRecord::PASSWORD_SIZE,
data/yapet-2.5/tests/converters/import/import.cc:264:14: [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.
std::snprintf(comment, yapet::PasswordRecord::COMMENT_SIZE,
data/yapet-2.5/libyacurs/src/curs.cc:324:28: [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.
char* crows = std::getenv("LINES");
data/yapet-2.5/libyacurs/src/curs.cc:325:28: [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.
char* ccols = std::getenv("COLUMNS");
data/yapet-2.5/libyacurs/src/eventqueue.cc:985:26: [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.
if ((stats_fn = std::getenv("LIBYACURS_EVT_STATS")) != 0) {
data/yapet-2.5/libyacurs/src/eventqueue.cc:1029:14: [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.
if (std::getenv("LIBYACURS_EVTCONNMAP_DBGFN") == 0) return;
data/yapet-2.5/libyacurs/src/eventqueue.cc:1032:30: [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.
std::ofstream f(std::getenv("LIBYACURS_EVTCONNMAP_DBGFN"),
data/yapet-2.5/libyacurs/src/yacursdbg.cc:35:39: [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.
char* _debugfile_name_ = std::getenv("LIBYACURS_DEBUG_LOGFILE");
data/yapet-2.5/libyacurs/src/yacursdbg.cc:44:30: [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.
if (std::getenv("LIBYACURS_EVTQUEUE") == 0) return;
data/yapet-2.5/libyacurs/src/yacursdbg.cc:49:30: [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.
if (std::getenv("LIBYACURS_FOCUSGRP") == 0) return;
data/yapet-2.5/libyacurs/src/yacursdbg.cc:54:30: [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.
if (std::getenv("LIBYACURS_FOCUSMGR") == 0) return;
data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog2.cc:96:25: [3] (random) drand48:
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.
while ((tmp = (int)(drand48() * 100) % 20) < 2)
data/yapet-2.5/src/converters/csv2yapet/main.cc:192:17: [3] (buffer) getopt:
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 ((c = getopt(argc, argv, ":chp:qs:V")) != -1) {
data/yapet-2.5/src/converters/yapet2csv/main.cc:190:17: [3] (buffer) getopt:
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 ((c = getopt(argc, argv, ":chp:qs:HV")) != -1) {
data/yapet-2.5/src/libs/cfg/cfg.cc:78:16: [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.
char* hd = getenv("HOME");
data/yapet-2.5/src/yapet/main.cc:213:17: [3] (buffer) getopt:
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 ((c = getopt(argc, argv, ":chir:sSt:V")) != -1) {
data/yapet-2.5/libyacurs/include/event.h:67: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 _name[MAX_NAME_LENGTH];
data/yapet-2.5/libyacurs/src/curs.cc:328:30: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
int _rows = std::atoi(crows);
data/yapet-2.5/libyacurs/src/curs.cc:329:30: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
int _cols = std::atoi(ccols);
data/yapet-2.5/libyacurs/src/eventqueue.cc:988:28: [2] (misc) open:
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).
_statsfile.open(stats_fn, std::ios::out | std::ios::trunc);
data/yapet-2.5/libyacurs/src/sigaction.cc:52: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.
std::memcpy(&_current_action.sa_mask, &mask, sizeof(sigset_t));
data/yapet-2.5/libyacurs/src/yacursdbg.cc:38:28: [2] (misc) open:
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).
_debugfile.open(_debugfile_name_,
data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog2.cc:396:18: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(selection1[i], __dir_up_data, 20 * sizeof(int));
data/yapet-2.5/libyacurs/tests/ui-interactive/resize3.cc:53: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.
char buff[32];
data/yapet-2.5/libyacurs/tests/ui-interactive/resize4.cc:54: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.
char buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/dynlabel1.cc:41: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 buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/dynlabel2.cc:41: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 buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/hrule1.cc:41: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 buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/packresize1.cc:41: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 buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/resize2.cc:43: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 buff[32];
data/yapet-2.5/libyacurs/tests/ui-non-interactive/vrule1.cc:41: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 buff[32];
data/yapet-2.5/src/converters/csv/csvline.cc:47: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv/csvline.cc:109: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv/csvline.cc:172: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv/csvstringfield.cc:91:17: [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[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:116: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:128: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/csv2yapet/main.cc:183: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 passwd[MAX_PASSWD];
data/yapet-2.5/src/converters/yapet2csv/csvexport.cc:69: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/yapet2csv/csvexport.cc:81: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/converters/yapet2csv/main.cc:181: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 passwd[MAX_PASSWD];
data/yapet-2.5/src/libs/cfg/cfg.cc:169: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 msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/cfg/cfg.cc:178:58: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
void CfgValInt::set_str(const std::string& s) { set(std::atoi(s.c_str())); }
data/yapet-2.5/src/libs/cfg/cfg.cc:340: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/cfg/cfgfile.cc:56: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/cfg/cfgfile.cc:81: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.
char line[YAPET::Consts::MAX_CONFIG_LINE_LENGTH];
data/yapet-2.5/src/libs/cfg/cfgfile.cc:92:17: [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[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE * 3];
data/yapet-2.5/src/libs/cfg/cfgfile.cc:106:17: [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[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/aes256.cc:89: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/aes256.cc:120: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/crypto.cc:52: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/crypto.cc:104: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/file.cc:101:17: [2] (misc) open:
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).
_yapetFile->open();
data/yapet-2.5/src/libs/crypt/file.cc:168:14: [2] (misc) open:
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).
oldFile->open();
data/yapet-2.5/src/libs/crypt/file.cc:179:17: [2] (misc) open:
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).
_yapetFile->open();
data/yapet-2.5/src/libs/crypt/key256.cc:121: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.
std::memcpy(saltBuffer, archAgnosticSalt.bytes, SALT_LENGTH);
data/yapet-2.5/src/libs/crypt/key256.cc:215: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/key448.cc:135: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.
char tmp[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/crypt/key448.cc:144: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.
std::memcpy(*_ivec, *keyHash, IVEC_LENGTH);
data/yapet-2.5/src/libs/file/filehelper.cc:43:14: [2] (misc) open:
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.open();
data/yapet-2.5/src/libs/file/filehelper.cc:51:14: [2] (misc) open:
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.open();
data/yapet-2.5/src/libs/file/filehelper.cc:57: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 msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/filehelper.cc:85: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 msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/filehelper.cc:93:16: [2] (misc) open:
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).
yapetFile->open();
data/yapet-2.5/src/libs/file/fileutils.cc:56: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/fileutils.cc:69: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/fileutils.cc:77: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/fileutils.cc:122: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/header10.cc:65: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/header10.cc:88: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/header10.cc:110: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/header10.cc:133: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.
std::memcpy(pointerToControlString, CONTROL_STRING, CONTROL_STRING_SIZE);
data/yapet-2.5/src/libs/file/header10.cc:139: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.
std::memcpy(pointerToSetTime, &passwordSetTimeInODSFormat,
data/yapet-2.5/src/libs/file/rawfile.cc:102:18: [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 = std::fopen(_filename.c_str(), READ_WRITE_EXISTING_MODE);
data/yapet-2.5/src/libs/file/rawfile.cc:104: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:115:18: [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 = std::fopen(_filename.c_str(), CREATE_NEW_MODE);
data/yapet-2.5/src/libs/file/rawfile.cc:117: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:139: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:160: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:181: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:196: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:214: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:235: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:245: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/rawfile.cc:258: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapet10file.cc:49: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.
std::memcpy(buffer, reinterpret_cast<const char*>(recognitionString()),
data/yapet-2.5/src/libs/file/yapet10file.cc:76:19: [2] (misc) open:
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).
void Yapet10File::open() {
data/yapet-2.5/src/libs/file/yapet10file.cc:79: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapet10file.cc:118: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapet10file.cc:145: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapet10file.cc:208: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapet20file.cc:66: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/file/yapetfile.cc:68:13: [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[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/glue/changepassword.cc:68: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/glue/promptpassword.cc:62: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/passwordrecord/passwordlistitem.cc:47: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.
std::memcpy(*_name, host, len);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:52: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.
std::memcpy(dest, src, len);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:80: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:91: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.
std::memcpy(*_name, *serialized + positionInBuffer, NAME_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:94: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.
std::memcpy(*_host, *serialized + positionInBuffer, HOST_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:97: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.
std::memcpy(*_username, *serialized + positionInBuffer, USERNAME_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:100: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.
std::memcpy(*_password, *serialized + positionInBuffer, PASSWORD_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:103: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.
std::memcpy(*_comment, *serialized + positionInBuffer, COMMENT_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:153: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.
std::memcpy(*serialized + positionInBuffer, *_name, NAME_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:156: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.
std::memcpy(*serialized + positionInBuffer, *_host, HOST_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:159: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.
std::memcpy(*serialized + positionInBuffer, *_username, USERNAME_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:162: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.
std::memcpy(*serialized + positionInBuffer, *_password, PASSWORD_SIZE);
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:165: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.
std::memcpy(*serialized + positionInBuffer, *_comment, COMMENT_SIZE);
data/yapet-2.5/src/libs/pwgen/pwgen.cc:141: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/pwgen/rngengine.cc:55:15: [2] (misc) open:
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).
auto fd{::open(DEV_URANDOM, O_RDONLY)};
data/yapet-2.5/src/libs/pwgen/rngengine.cc:57: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/ui/mainwindow.cc:688: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.
std::memcpy(buffer, *fileVersion, fileVersion.size());
data/yapet-2.5/src/libs/utils/securearray.cc:56: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.
char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
data/yapet-2.5/src/libs/utils/securearray.cc:82: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.
std::memcpy(_array, other._array, _size);
data/yapet-2.5/src/libs/utils/securearray.cc:99: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.
std::memcpy(_array, other._array, _size);
data/yapet-2.5/src/libs/utils/securearray.cc:168: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.
std::memcpy(_array, source._array, _size);
data/yapet-2.5/src/libs/utils/securearray.cc:177: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.
std::memcpy(_array, source._array, _size);
data/yapet-2.5/src/libs/utils/securearray.cc:191: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.
std::memcpy(*result, str, len);
data/yapet-2.5/src/libs/utils/securearray.cc:207: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.
std::memcpy(*secureArray, ptr, size);
data/yapet-2.5/src/libs/utils/securearray.cc:217: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.
std::memcpy(*result, *a, aSize);
data/yapet-2.5/src/libs/utils/securearray.cc:219: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.
std::memcpy(ptrToBDest, *b, bSize);
data/yapet-2.5/src/yapet/main.cc:185: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 buff[512];
data/yapet-2.5/src/yapet/main.cc:247:57: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
YAPET::Globals::config.timeout.set(std::atoi(optarg));
data/yapet-2.5/tests/converters/import/import.cc:251: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.
char name[yapet::PasswordRecord::NAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:252: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.
char host[yapet::PasswordRecord::HOST_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:253: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.
char username[yapet::PasswordRecord::USERNAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:254: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.
char password[yapet::PasswordRecord::PASSWORD_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:255: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.
char comment[yapet::PasswordRecord::COMMENT_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:307: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.
char name[yapet::PasswordRecord::NAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:308: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.
char host[yapet::PasswordRecord::HOST_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:309: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.
char username[yapet::PasswordRecord::USERNAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:310: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.
char password[yapet::PasswordRecord::PASSWORD_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:311: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.
char comment[yapet::PasswordRecord::COMMENT_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:364: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.
char name[yapet::PasswordRecord::NAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:365: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.
char host[yapet::PasswordRecord::HOST_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:366: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.
char username[yapet::PasswordRecord::USERNAME_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:367: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.
char password[yapet::PasswordRecord::PASSWORD_SIZE];
data/yapet-2.5/tests/converters/import/import.cc:368: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.
char comment[yapet::PasswordRecord::COMMENT_SIZE];
data/yapet-2.5/tests/file/filehelper.cc:59:21: [2] (misc) open:
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).
auto fd = ::open(TEST_FILE, O_CREAT | O_TRUNC | O_RDWR,
data/yapet-2.5/tests/file/filehelper.cc:153:18: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/filehelper.cc:173:18: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/filehelper.cc:193:18: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/filehelper.cc:213:18: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/fileutils.cc:60:21: [2] (misc) open:
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).
auto fd = ::open(TEST_FILE, O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO);
data/yapet-2.5/tests/file/yapet10file.cc:67:17: [2] (misc) open:
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).
newFile.open();
data/yapet-2.5/tests/file/yapet10file.cc:71:20: [2] (misc) open:
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).
int fd = ::open(TEST_FILE, O_CREAT | O_WRONLY, S_IWUSR | S_IRUSR);
data/yapet-2.5/tests/file/yapet10file.cc:76:42: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(yapet10File.open(), yapet::FileFormatError);
data/yapet-2.5/tests/file/yapet10file.cc:82:42: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(yapet10File.open(), yapet::FileFormatError);
data/yapet-2.5/tests/file/yapet10file.cc:89:25: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:96:22: [2] (misc) open:
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).
yapet10File2.open();
data/yapet-2.5/tests/file/yapet10file.cc:103:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:111:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:121:25: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:133:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:143:25: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:154:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:162:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:193:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:203:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet10file.cc:218:21: [2] (misc) open:
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).
yapet10File.open();
data/yapet-2.5/tests/file/yapet20file.cc:71:17: [2] (misc) open:
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).
newFile.open();
data/yapet-2.5/tests/file/yapet20file.cc:75:20: [2] (misc) open:
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).
int fd = ::open(TEST_FILE, O_CREAT | O_WRONLY, S_IWUSR | S_IRUSR);
data/yapet-2.5/tests/file/yapet20file.cc:80:42: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(yapet20File.open(), yapet::FileFormatError);
data/yapet-2.5/tests/file/yapet20file.cc:86:42: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(yapet20File.open(), yapet::FileFormatError);
data/yapet-2.5/tests/file/yapet20file.cc:93:25: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:100:22: [2] (misc) open:
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).
yapet20File2.open();
data/yapet-2.5/tests/file/yapet20file.cc:107:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:117:25: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:126:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:134:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:150:25: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:161:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:171:25: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:184:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:192:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:225:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:235:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapet20file.cc:250:21: [2] (misc) open:
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).
yapet20File.open();
data/yapet-2.5/tests/file/yapetfile.cc:70:10: [2] (misc) open:
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).
void open() { openRawFile(); }
data/yapet-2.5/tests/file/yapetfile.cc:104:35: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(file.open(), yapet::FileError);
data/yapet-2.5/tests/file/yapetfile.cc:109:14: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/yapetfile.cc:115:21: [2] (misc) open:
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).
auto fd = ::open(TEST_FILE, O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO);
data/yapet-2.5/tests/file/yapetfile.cc:122:35: [2] (misc) open:
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).
CPPUNIT_ASSERT_THROW(file.open(), yapet::FileInsecureError);
data/yapet-2.5/tests/file/yapetfile.cc:126:21: [2] (misc) open:
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).
auto fd = ::open(TEST_FILE, O_CREAT, S_IRUSR | S_IWUSR);
data/yapet-2.5/tests/file/yapetfile.cc:133:14: [2] (misc) open:
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.open();
data/yapet-2.5/tests/file/yapetfile.cc:138:21: [2] (misc) open:
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).
auto fd = ::open(TEST_FILE, O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO);
data/yapet-2.5/tests/file/yapetfile.cc:145:14: [2] (misc) open:
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.open();
data/yapet-2.5/libyacurs/include/yacurscurses.h:121:34: [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).
std::memset(tmp_ptr, 0, std::strlen(tmp_ptr));
data/yapet-2.5/libyacurs/include/yacurscurses.h:144:34: [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).
std::memset(tmp_ptr, 0, std::strlen(tmp_ptr));
data/yapet-2.5/libyacurs/include/yacurscurses.h:167:34: [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).
std::memset(tmp_ptr, 0, std::strlen(tmp_ptr));
data/yapet-2.5/libyacurs/include/yacurscurses.h:190:34: [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).
std::memset(tmp_ptr, 0, std::strlen(tmp_ptr));
data/yapet-2.5/libyacurs/src/curswin.cc:329:38: [1] (buffer) _mbslen:
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 (space < static_cast<int16_t>(_mbslen)) {
data/yapet-2.5/libyacurs/src/event.cc:52:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(_name, name.c_str(), MAX_NAME_LENGTH - 1);
data/yapet-2.5/libyacurs/src/event.cc:57:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(_name, et._name, MAX_NAME_LENGTH);
data/yapet-2.5/libyacurs/src/event.cc:65:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(_name, rhs._name, MAX_NAME_LENGTH);
data/yapet-2.5/libyacurs/tests/ui-interactive/app1.cc:105:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/app1.cc:121:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/checkbox1.cc:148:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/checkbox1.cc:164:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/dialog1.cc:57:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/dialog1.cc:82:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog2.cc:113:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/filedialog2.cc:155:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/focus1.cc:274:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/focus1.cc:290:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/input1.cc:97:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/input1.cc:121:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/inputbox1.cc:78:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/inputbox1.cc:94:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/listbox1.cc:80:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/listbox1.cc:96:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/listbox2.cc:746:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/listbox2.cc:762:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/lockscreen1.cc:128:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/lockscreen1.cc:155:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox1.cc:34:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox1.cc:50:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox2.cc:34:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox2.cc:50:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox3.cc:34:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/messagebox3.cc:50:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/packremove.cc:48:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/packremove.cc:73:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/radiobox1.cc:148:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-interactive/radiobox1.cc:164:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:34:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:51:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:68:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:79:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:95:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:116:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:141:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:163:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:189:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:206:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:223:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:234:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:250:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:271:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:296:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/cursorbuf1.cc:318:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:84:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:96:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:113:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:125:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:137:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:149:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:155:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:161:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:167:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:173:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin1.cc:179:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:84:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:96:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:113:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:125:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:137:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:149:13: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:155:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:161:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:167:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:173:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/curswin2.cc:179:9: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/libyacurs/tests/ui-non-interactive/listbox1.cc:267:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(70000);
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:137:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
inline char read(std::ifstream& csvFile, char& lookAhead) {
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:158:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
currentCharacter = read(csvFile, lookAhead);
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:180:21: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
line += read(csvFile, lookAhead);
data/yapet-2.5/src/converters/csv2yapet/csvimport.cc:196:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
line += read(csvFile, lookAhead);
data/yapet-2.5/src/converters/csv2yapet/main.cc:201:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(passwd, optarg, MAX_PASSWD - 1);
data/yapet-2.5/src/converters/csv2yapet/main.cc:272:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(passwd, pw1.c_str(), MAX_PASSWD - 1);
data/yapet-2.5/src/converters/yapet2csv/csvexport.cc:106:58: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = yapetFile->read();
data/yapet-2.5/src/converters/yapet2csv/main.cc:199:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(passwd, optarg, MAX_PASSWD - 1);
data/yapet-2.5/src/converters/yapet2csv/main.cc:260:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(passwd, pw1.c_str(), MAX_PASSWD - 1);
data/yapet-2.5/src/libs/cfg/cfgfile.cc:83: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).
if (std::strlen(line) < 1) continue;
data/yapet-2.5/src/libs/crypt/file.cc:129:35: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<PasswordListItem> File::read() {
data/yapet-2.5/src/libs/crypt/file.h:81:40: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> read();
data/yapet-2.5/src/libs/file/rawfile.cc:125:39: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::pair<SecureArray, bool> RawFile::read(std::uint32_t size) {
data/yapet-2.5/src/libs/file/rawfile.cc:148:39: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::pair<SecureArray, bool> RawFile::read() {
data/yapet-2.5/src/libs/file/rawfile.cc:169:12: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return read(hostRecordSize);
data/yapet-2.5/src/libs/file/yapet10file.cc:116:27: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto result = rawFile.read(recognitionStringSize());
data/yapet-2.5/src/libs/file/yapet10file.cc:143:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto resultPair{rawFile.read()};
data/yapet-2.5/src/libs/file/yapet10file.cc:164:34: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((resultPair = rawFile.read()).second != false) {
data/yapet-2.5/src/libs/file/yapet20file.cc:64:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto resultPair{rawFile.read()};
data/yapet-2.5/src/libs/passwordrecord/passwordlistitem.cc:42: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).
auto stringLengthIncludingZero = std::strlen(host) + 1;
data/yapet-2.5/src/libs/passwordrecord/passwordrecord.cc:61: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).
std::strlen(src) + 1, maxLen);
data/yapet-2.5/src/libs/pwgen/rngengine.cc:73:20: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int retval = ::read(fd, &byteCache, BYTE_CACHE_SIZE);
data/yapet-2.5/src/libs/ui/mainwindow.cc:469:37: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
recordlist->set(_yapetFile->read());
data/yapet-2.5/src/libs/ui/mainwindow.cc:555:37: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
recordlist->set(_yapetFile->read());
data/yapet-2.5/src/libs/utils/securearray.cc:183: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).
auto len = std::strlen(str) + 1;
data/yapet-2.5/tests/converters/import/import.cc:79:57: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file->read();
data/yapet-2.5/tests/converters/import/import.cc:129:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/converters/import/import.cc:155:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/converters/import/import.cc:181:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/converters/import/import.cc:208:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/converters/import/import2.cc:66:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/crypt/file_aes256.cc:240:60: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/crypt/file_aes256.cc:340:27: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actual{file2.read()};
data/yapet-2.5/tests/crypt/file_aes256.cc:405:52: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/crypt/file_aes256.cc:461:31: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
CPPUNIT_ASSERT_THROW(file.read(), yapet::EncryptionError);
data/yapet-2.5/tests/crypt/file_blowfish.cc:233:60: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/crypt/file_blowfish.cc:333:27: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actual{file2.read()};
data/yapet-2.5/tests/crypt/file_blowfish.cc:397:60: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/crypt/file_blowfish.cc:451:35: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
CPPUNIT_ASSERT_THROW(file.read(), yapet::EncryptionError);
data/yapet-2.5/tests/crypt/foreign.cc:96:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto passwords{file.read()};
data/yapet-2.5/tests/crypt/key256.cc:20:53: [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).
static_cast<yapet::SecureArray::size_type>(std::strlen(password));
data/yapet-2.5/tests/crypt/key448.cc:23:53: [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).
static_cast<yapet::SecureArray::size_type>(std::strlen(password));
data/yapet-2.5/tests/crypt/passwordchange_exerciser.cc:125:56: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> list = file.read();
data/yapet-2.5/tests/file/rawfile.cc:72:35: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
CPPUNIT_ASSERT_THROW(file.read(), yapet::FileError);
data/yapet-2.5/tests/file/rawfile.cc:73:35: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
CPPUNIT_ASSERT_THROW(file.read(1), yapet::FileError);
data/yapet-2.5/tests/file/rawfile.cc:99:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actualPair = file.read(sizeof(fileContent));
data/yapet-2.5/tests/file/rawfile.cc:116:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actualPair = file.read(1);
data/yapet-2.5/tests/file/rawfile.cc:119:27: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
actualPair = file.read();
data/yapet-2.5/tests/file/rawfile.cc:134:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actualPair = file.read();
data/yapet-2.5/tests/file/rawfile.cc:164:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto actualPair = file.read();
data/yapet-2.5/tests/file/rawfile.cc:190:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
auto resultPair = file.read();
data/yapet-2.5/tests/preload/checkmasterpwchange.cc:91:55: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> lst = testfile.read();
data/yapet-2.5/tests/preload/checkmasterpwchange.cc:95:15: [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 (!std::equal(lst.begin(), lst.end(), control_data.begin())) abort();
data/yapet-2.5/tests/preload/checktestpwrecord.cc:91:55: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::list<yapet::PasswordListItem> lst = testfile.read();
data/yapet-2.5/tests/preload/checktestpwrecord.cc:95:15: [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 (!std::equal(lst.begin(), lst.end(), control_data.begin())) abort();
ANALYSIS SUMMARY:
Hits = 330
Lines analyzed = 51138 in approximately 1.30 seconds (39449 lines/second)
Physical Source Lines of Code (SLOC) = 31407
Hits@level = [0] 80 [1] 132 [2] 171 [3] 14 [4] 11 [5] 2
Hits@level+ = [0+] 410 [1+] 330 [2+] 198 [3+] 27 [4+] 13 [5+] 2
Hits/KSLOC@level+ = [0+] 13.0544 [1+] 10.5072 [2+] 6.30433 [3+] 0.859681 [4+] 0.41392 [5+] 0.0636801
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.