Difference between revisions of "Incident 20211212 Bittrex"
VeriBlockTim (talk | contribs) (Created page with "See: Incident_History '''Status:''' Open '''Expected Resolution''': TBD '''Summary:''' Bittrex Global NodeCore wallet is down for "Currency Maintenance" due to security...") |
VeriBlockTim (talk | contribs) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
See: [[Incident_History]] | See: [[Incident_History]] | ||
| − | '''Status:''' | + | '''Status:''' Closed |
| − | '''Expected Resolution''': | + | '''Expected Resolution''': Jan 6, 2022, 1pm ET. New NodeCore instance with updated log4j deployed. |
'''Summary:''' Bittrex Global NodeCore wallet is down for "Currency Maintenance" due to security concerns around global Log4j security bug | '''Summary:''' Bittrex Global NodeCore wallet is down for "Currency Maintenance" due to security concerns around global Log4j security bug | ||
| Line 14: | Line 14: | ||
FYI, there is a public API: https://api.bittrex.com/api/v1.1/public/getcurrencies | FYI, there is a public API: https://api.bittrex.com/api/v1.1/public/getcurrencies | ||
| + | |||
| + | [Update] log4j 2.16 required | ||
| + | |||
| + | [Update] log4j 2.17 required - https://logging.apache.org/log4j/2.x/security.html | ||
| + | |||
| + | [Update] log4j 2.17.1 required | ||
Latest revision as of 21:09, 6 January 2022
See: Incident_History
Status: Closed
Expected Resolution: Jan 6, 2022, 1pm ET. New NodeCore instance with updated log4j deployed.
Summary: Bittrex Global NodeCore wallet is down for "Currency Maintenance" due to security concerns around global Log4j security bug
The wallet went down on Dec 12th, around 07:00pm ET.
The VeriBlock dev team has reached out to Bittrex support team.
The network remains healthy.
FYI, there is a public API: https://api.bittrex.com/api/v1.1/public/getcurrencies
[Update] log4j 2.16 required
[Update] log4j 2.17 required - https://logging.apache.org/log4j/2.x/security.html
[Update] log4j 2.17.1 required
