CVE-2024-57695

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

EUVD-2024-55066

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

CVE-2024-57695

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

CVE-2024-57695

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

CVE-2024-57695

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

CVE-2024-57695

An issue in Agnitum Outpost Security Suite 7.5.3 3942.608.1810 and 7.6 3984.693.1842 allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 4164.652.1856 from December 17, 2012...

Agnitum Outpost Security Suite 安全漏洞

Agnitum Outpost Security Suite is an Internet security suite from the Russian company Agnitum. A security vulnerability exists in Agnitum Outpost Security Suite versions 7.5.3 and 7.6, which stems from a flaw in the lock function that could allow a local attacker to execute arbitrary code...

CVE-2024-57695

The CVE-2024-57695 entry concerns Agnitum Outpost Security Suite versions 7.5.3 (3942.608.1810) and 7.6 (3984.693.1842), where a local attacker can execute arbitrary code via the lock function. The vendor addressed this by releasing version 8.0 (4164.652.1856) on December 17, 2012. Connected docu...

PT-2025-46346

Name of the Vulnerable Software and Affected Versions Agnitum Outpost Security Suite versions 7.5.3 3942.608.1810 through 7.6 3984.693.1842 Description A local attacker can execute arbitrary code via the lock function. Recommendations Update to version 8.0 4164.652.1856...

PCI: Add missing bridge lock to pci_bus_lock()

...

Oracle Linux 5 : Oracle / Enterprise / Linux / 5.5 / kernel (ELSA-2010-0178)

The remote Oracle Linux 5 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2010-0178 advisory. - fs gfs2: locking fix for potential dos Steven Whitehouse 572390 CVE-2010-0727 - net sctp: backport cleanups for ootb handling Neil Horman 555667...

MuteBond is susceptible to DOS

Lines of code Vulnerability details Proof of Concept Observe that if timeToTokens is called with locktime = 1 week, amount 52, it will return 0. function timeToTokensuint256 amount, uint256 locktime internal pure returns uint256 uint256 weektime = 1 weeks; uint256 maxlock = 52 weeks;...

Unable to release funds deposited through Lock-extendLock

Lines of code Vulnerability details Impact Users depositing tig assets to the bondNFT through the Lock contract could find themselves unable to release their funds. The only explanation the user would receive is an "Arithmetic over/underflow" error. This issue greatly deteriorates the user...

AuraLocker.sol lock() can be used to dos user

Lines of code Vulnerability details Impact User funds permanently stuck in AuraLocker Proof of Concept The lock function allows anyone to deposit and lock tokens for another address. If the most recent lock is not expired, it pushes a new lock to the array of locks for that user in the following...

Reentrancy allows attacker to lock the funds deposited in the contract

Handle tqts Vulnerability details Impact It is possible for attackers to exploit a reentrancy issue in lockuint256,uint256,address that would allow them to lock all funds deposited prior to the attack. Proof of Concept The problem lies in the lockuint256,uint256,address function, that transfers t...

Missing noreentrant modifier on merge() and updateDistribution(), can reenter from the _lock()

Handle Fitraldys Vulnerability details Impact A user can call lock that will call lock, that eventually will call safeMint, the safeMint function will make an external call to the destination address through checkOnERC721Received, and since the merge and updateDistribution didnt have noreentrant...

The reentrancy vulnerability in _safeMint can allow an attacker to steal all rewards

Handle cccz Vulnerability details Impact There is a reentrancy vulnerability in the safeMint function function safeMint address to, uint256 tokenId, bytes memory data internal virtual mintto, tokenId; require checkOnERC721Receivedaddress0, to, tokenId, data, "ERC721: transfer to non ERC721Receive...

Reentrancy at lock can lead to wrong accounting

Handle kenzo Vulnerability details The lock function calls safeMint in the midst of it. This can lead to reentry to updateDistribution, thereby ruining contract invariants. Impact At worst case, loss of user funds: distributableXDEFI will be set to be bigger than it really is, and so when a...

CVE-2012-6111

gnome-keyring does not discard stored secrets when using gnomekeyringlockallsync function...