In adminutil, we call va_start() in servssl_error() and servssl_warn() functions, but we never call va_end(). We should be calling va_end() in these functions.
Created attachment 492503 [details] Patch for cov#10770
Pushed to master. Thanks to Rich for his review! Counting objects: 16, done. Delta compression using up to 2 threads. Compressing objects: 100% (10/10), done. Writing objects: 100% (10/10), 1.14 KiB, done. Total 10 (delta 7), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/adminutil.git ba20398..f20dc1b master -> master
Created attachment 492924 [details] Additional patch The previous patch had a typo in the va_end() function name. This fixes that typo.
Pushed additional patch to master. Counting objects: 9, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 531 bytes, done. Total 5 (delta 4), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/adminutil.git 5590b3e..2db116d master -> master
389-adminutil-1.1.14-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/389-adminutil-1.1.14-1.fc15
389-adminutil-1.1.14-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/389-adminutil-1.1.14-1.fc14
389-adminutil-1.1.14-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/389-adminutil-1.1.14-1.fc13
389-adminutil-1.1.14-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/389-adminutil-1.1.14-1.el5
389-adminutil-1.1.14-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
389-adminutil-1.1.14-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
389-adminutil-1.1.14-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
Need to be verified by dev as co-verity issue. Thanks, Amita
This issue does not show up in our current coverity scans of adminutil. Marking as VERIFIED.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.